Windows phone user interface guidelines
Represents a control that a user can select check or clear uncheck. Represents a control with a single piece of content. This might be used in a button for example to define a button with an image. Displays the content of a ContentPresenter. Represents the base class for UI elements that use a ControlTemplate to define their appearance.
Defines a flexible grid area that consists of columns and rows. Represents a button control that displays a hyperlink. Implements a rectangular surface that displays ink strokes. Contains a list of selectable items.
Represents an object that contains audio, video, or both. Displays a message to the user and optionally prompts for a response. Enables users to open a multi-resolution image, which can be zoomed in on and panned across. Provides a base class for all Panel elements.
Use Panel elements to position and arrange child objects in Silverlight-based applications. Represents a control for entering passwords. Represents a control that indicates the progress of an operation. Following is the Controls not supported in Windows Phone. But some library is provide in Silverlight Toolkit Library.
Privacy policy. This topic defines what user interface guidelines are and describes why following guidelines exclusively might not be the best strategy. UI guidelines are collections of recommendations that designers and developers follow when creating the user interface for applications.
Guidelines can include:. These principles can include the expression of a fundamental design philosophy, assumptions about human behavior, a design methodology, and concepts embodied in the interface.
Most, if not all, major software platforms have published guidelines for user interface design. Many individual companies and organizations have their own set of documented UI rules or styles for interface design that developers in that company use. This is common in large companies especially, where a suite of applications is created internally.
As an application designer, following UI guidelines helps ensure that the product allows users to apply skills they've already learned to common tasks and learn new tasks more easily. However, you cannot rely solely on guidelines to ensure the usability of your product. UI guidelines are often too general. Yet it's that very generality that makes them difficult to apply. See visual examples of controls in Windows-based, desktop apps and get links to guidelines for each control.
Commands are actions users can take while using your app. Learn the guidelines for adding commands to your app's menus, ribbons, and toolbars. Text includes any text users can see in your app. Review these guidelines on the use of UI text, style, and tone for your apps. Messages are any kind of message users need or want to see as they use your app.
Learn how to present errors, warning, confirmations, and notifications in your app. Interaction is the variety of ways users interact with your app, including touch, keyboard, mouse, and so on. Use these guidelines to create intuitive and distinctive experiences that are optimized for touch but work consistently across input devices. Windows are the main "canvases" or UI surfaces of your desktop app, including the main windows itself and pop-ups, dialogs, and wizards.