Select a language to translate this page!
Powered by Microsoft® Translator
Interaction on a mobile device utilizes a series of finger gestures. Flicking, panning, pinching and tapping, for example, all require finger gestures to successfully navigate an experience. Given the amount of common controls provided by WP7, interactive elements are bound to share similarities in finger gestures. Understanding the use of common controls will ensure an application is free of conflict upon interaction.
Make your life easy The WP7 SDK provides a set of controls common throughout the platform. Incorporating common controls within your application will save development time and maintain a consistent experience. Re-creating controls that mimic the aesthetics and behaviors may alter the interaction, degrading a familiar experience within the platform. Make your life easy—utilize the controls supplied with the SDK.
Use them right Consider the interaction of controls before moving forward, doing so will avoid conflicting gestures. For example, placing a map control in a panorama. Both controls require the same finger gesture to swipe—interacting with one control could potentially override functionality and behavior of the other. Same thing applies for using the toggle or swipe controls on pages with pivots or panoramas.
No “Back” or “Close” buttons A good reminder also when talking about controls, “Back” and “Close” actions are handled by the hardware button therefore no visual affordances should be present within the interface.
Something that the usability guru Jakob Nielsen used to say about the web applies here as well; Users of your app will spend most of their time on other apps and will be expecting your app to behave like those. Those apps wouldn’t have “Back” or “Close” buttons so even if you believe your app needs it, refrain from use them.
- Alfred Astort Follow the Windows Phone Design Team on Twitter: @WPdesignteam
Any chance of seeing a reference application that has all the recommended page transitions (for different "types" of pages)?
If you say no back buttons so why in build in apps are you useing them? For example in wizard when you are register a phone with live id and in a lot of other places.
The lack of support for proper modal dialogs is confusing. If you navigate to a whole other page - does back exit me out of the app or does back get me out of the dialog. This is the mental model that users have to keep in their head and it's just too hard.
The panorama is difficult as well, in my experience watching folks use it people get completely lost. I spent half my time making sure the background was good enough that people didn't go "oh god oh god where did my thing go". I'll never use panorama for another app.
I don't like how the default Button in the sdk does not act the same as the default button used in the os. it doesn't move down where you press. would be nice to see the default sdk elements behave exactly identical to the rest of the os. consistency is key, always.