Windows 8 mobile ux guidelines

Multi - resolution apps for Windows Phone 8. Users recognize certain icons to mean certain things, either because they are used elsewhere in the device or because they are commonly associated with something else. For example:. Do not repurpose existing icons. This includes its behavior when implementing secondary tiles please refer to section 4. They are designed to allow quick and easy access to content and are generally not used as an entry point for exploration.

For example, a pinned album from music and video will play the album when tapped. The tile serves as a specific purpose — go to the album and play it. Tapping on one of these tiles takes the user into the contact card pivot where they can see all the information and tasks related to that specific contact. Please do not repurpose existing icons. When a user launches an application by tapping on a secondary tile, pressing the hardware back button should exit the application i. The behavior of the hardware back button should not be altered in any way.

Lens design guidelines for Windows Phone. This effect is available from the Silverlight for Windows Phone Toolkit. Indeterminate progress bar.

  • Best Practices for UX Design in Windows 8 Apps;
  • best low vision cordless phone.
  • facebook app for blackberry bold 9000!
  • blackberry 9800 driver windows 8.

Never use angry or mechanical tones in the application. These are just recommendations from different cases studies that are usually application specific. So, feel free to do what is right for your application taking into consideration some success factions like:. Once you have the basics down and have begun to piece together the visuals for your application, refer to the guidelines in this article. They will help you avoid some of the most common mistakes that I have seen when reviewing designs or during building my own apps. You must be logged in to post a comment.

Really Awesome! I was just wondering about one thing. You should show "John Smith" in big font with smaller "name" underneath. Content over chrome and all that stuff. Thanks for the great guide! Some of the pictures though, for instance this one media. Any chance of getting that fixed? Cato it opens well on my side, could you check and let me know. Also Kym you are right is about content over chrome. Dina Helmy — Seems that it was either Chrome or the proxy Chrome is passing through at work that caused the issue.

Sorry for the trouble, and keep the great blog posts coming! This is great article. I do have one suggestion. This is awesome piece of an article, it reminds me from a dummy WP developer to be able now implement the guidelines in my application. Dina, can you provide more useful links about UX guidelines for Windows Phone 8? I can't find any other article so objective as this. Backgrounds - Backgrounds are discouraged. Instead, use any accent colors on the text foreground Layouts - Use text size and color to establish list item hierarchy.

Enhancements - List enhancements should not be used unless they are distinct from one another, such as in a menu. Scrollable Content -If you have scrollable content on your page, you should put 95px bottom padding at the end of your content. For example, here is a simple page that is slightly higher than the visible area: Gesture Competition - Controls that provide a horizontally scrollable area or take a horizontal swipe gesture are not permitted in the pivot control as the horizontal swipe gesture is reserved for changing pivot pages.

  • A window to the world.
  • samsung galaxy s6 edge specs phonearena?
  • Learning to speak Metro.

Application Bar - Common actions such as refresh, search and settings should be placed in an application bar. Scrollable Panes - Panorama panes should either scroll vertically or horizontally. Not both. Navigation - Floating buttons should be avoided. Interactive Content - Minimize the use interactive content on the panorama forms, search boxes etc.

Number of Panes - A maximum of five panes are recommended. Background - Panorama controls should have a background. Title - The panorama title should be animated. Section Titles - The font size should be larger than the corresponding content.

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question. Home Questions Tags Users Unanswered.

Design and code Windows apps

Crudely speaking, once the app is started you can configure it or connect to a server. Any thoughts much appreciated. Also check: Its still in work and not complete yet, but you can get some information here: Browse, My Music, Radio, and Featured. Each contains enough content to constitute a Metro application all on its own. Our challenge was to unite them.

Design basics

We began by implementing a navigation bar to provide access to each of the four different sections, as well as the main Hub home screen from any page of the application. After showing our wireframes to Microsoft employees, they advised us to use the initial hub screen to showcase the different sections. This, however, meant adding an additional level of navigation to an already deep hierarchy — deeper the 3 levels dictated by Microsoft.

If a user was interested in Scandinavian Pop, for instance, he would have to travel from:.

Windows Phone Design

The challenge was allowing the user to return to the Home screen without having to continue tapping on the Back button. Some applications solve this by placing a Home button in the app bar —although this is generally considered against proper Windows 8 Metro design. Instead, we decided to use a dropdown menu next to the page headers that provides access to the Home page, the four section pages and, if applicable, sibling pages such as subgenres.

Contrary to Metro style design patterns, we initially used hubs and section pages to break down pages that contained large amounts of content, even when they were not pages at the very top of the hierarchy. Each of these groups was linked to a section page that provided the remaining content. When we showed our design to Microsoft designers, they advised us to keep all the content for all the groups on a single, wide page.

How to design a Windows 8 Metro style app starting from an e

This was one case in which we decided to go against the advice we received — there were simply too many cases in which the number of albums and similar artists would make the page too wide to browse with ease. Pavarotti, for instance, has over albums. Having a single page would make it difficult to find a specific album, and require semantic zoom to make users aware of the existence of the other sections.

Windows 8 design guidelines encourage hiding the chrome, or persistent navigational elements of an app. Those navigational elements are available by going back to home or are tucked away in dropdowns from titles. This sounds like a constraint, but it really is a solid principle for mobile and touch applications in general. Rhapsody users are accustomed to having the music player visible on every screen. Initially, we created a sidebar that showed the cover art of the album currently playing, buttons to control the music and the queue.

Users could hide and show the sidebar by swiping it on and off the left edge of the screen. MSDN suggests placing players in the navigation bar top of the screen , whilst all other music applications seem to have it in the app bar bottom of the screen. In the end, we decided to place it in the navigation bar to free up the app bar for other controls.