Implementing Windows 8 Design Principles


Published on

Windows 8 marks a complete shift in design principles for the Windows platform. To stay relevant as a developer on the Windows platform, you have to learn to implement the new Windows 8 design principles. In this session, we will cover what you need to know about what has changed and what hasn't. We will look at how you, the developer, can leverage these design principles from the perspective you know best: the code.

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Implementing Windows 8 Design Principles

  1. 1. Implementing Windows 8Design PrinciplesBrent EdwardsAssociate Principal
  2. 2. Get Started
  3. 3. Build your app: GenerationApp Launch your Windows 8 App in 30 days Generation App  Online training and tips from insiders  Tele-support with a Windows 8 architect  Exclusive one-on-one WinRT and Windows UX design consultation Sign up at
  4. 4. Local Events• Twin Cities Windows 8 User Group – 4th Tuesday of Month –• Windows 8 JavaScript and HTML Camp – Oct 4th –• Windows 8 Developer Camp – Oct 9th –• Windows 8 Hackathon – Oct 10th –
  5. 5. Level Set• Designer?• Developer?• Aren’t Designer but play one at work?
  6. 6. Windows 8 Design PrinciplesWhat are they?
  7. 7. Windows 8 Design Principles• Do more with less – Content before chrome• Pride in craftsmanship – Styling, layout, typography – The details matter• Be fast and fluid – Design for touch with motion and ergonomics in mind• Authentically digital – Remember that user is interacting with computerized device• Win as one – Use contracts to work with other apps
  8. 8. That’s awful designer-likeWhat about us developer types?
  9. 9. Approach Your UI Differently• Design for Touch• Put Content Before Chrome – Full Screen Content• Leverage Adaptive Layout• Be Authentically Digital – Don’t try to mimic the real world
  10. 10. Design for Touch
  11. 11. Windows 8 Touch Language• Design your app to be touch first Source:
  12. 12. How Does Touch Change Things?• Targets must be bigger Source:• 40 x 40px – Recommended minimum size – IF a wrong touch can be fixed in 1-2 gestures or within 5 seconds• 50 x 50px – Recommended for actions with severe consequences – Close, Delete – Requires 2 gestures, 5 seconds, or major context change to correct
  13. 13. What Doesn’t Work With Touch?• Listbox and ComboBox – Don’t have a good form factor for touch UI – Still available, but their use is discouraged
  14. 14. Content Before Chrome
  15. 15. Content Before Chrome Source:
  16. 16. Content Before Chrome• What is Chrome? – Chrome is anything that isn’t CONTENT – Chrome is clutter• Drop the clutter – Focus on what is important – Let the rest fade away• Example: – Commands don’t have to take up screen real estate • Get rid of menu bars • Swipe from edge for system commands • Swipe from bottom for your app commands in AppBar
  17. 17. Adaptive Layout
  18. 18. Adaptive Layout• What is Adaptive Layout? – A layout that adapts to the available screen real estate Source:
  19. 19. Adaptive Layout[Demo]
  20. 20. Adaptive Layout• Snap View• GridView• ListView
  21. 21. Snap View Source:
  22. 22. Snap View• 320px Fixed Width• Matches Height of Screen• Allows for multitasking
  23. 23. GridView• First thing you see with Start Screen• Primary way to display data• Scrolls Horizontally• Uses Rows and Columns• Can display grouped content – Using CollectionViewSource
  24. 24. GridView[Demo]
  25. 25. ListView• Exactly the same as GridView EXCEPT: – Scrolls Vertically – Uses Rows• Works great for Snap View
  26. 26. ListView[Demo]
  27. 27. Authentically DigitalDon’t try to mimic the real world
  28. 28. Semantic Zoom• Lets user quickly navigate large amounts of data with touch gestures• 2 Levels – Zoomed Out • The Forest – Zoomed In • The Trees
  29. 29. Semantic Zoom[Demo]
  30. 30. FlipView• ItemsControl to view a single item at a time from a collection• Navigate between items with swipe gesture• Good for a small number of items
  31. 31. FlipView[Demo]
  32. 32. AppBarMore Content Before Chrome
  33. 33. AppBar• Menu Bars are clutter – Not CONTENT – Commands aren’t needed constantly• Only show when needed – Swipe from edge for system commands – Swipe from bottom for your app commands in AppBar
  34. 34. AppBar[Demo]
  35. 35. Recap• Design for Touch• Utilize Content Before Chrome – Full Screen Content• Leverage Adaptive Layout• Be Authentically Digital – Don’t try to mimic the real world• Developers can make good looking apps too
  36. 36. Questions?
  37. 37. Brent EdwardsAssociate Principal Consultant with