UX checklist for Windows Store apps
To make app certification easy, and to deliver a good user experience, use this checklist to verify that your app follows the UX guidelines.
Required
The following are the highest priority UX guidelines for your app. You must follow all guidance in this section to get your app certified for the Windows Store.
| Check | Description | Guidance |
|---|---|---|
| [ ] | The app must offer customers unique, creative value. | Planning Windows Store apps |
| [ ] | The app must be more than a website wrapped as a Windows Store app. | Planning Windows Store apps |
| [ ] | Each app must display one tile after it is installed. The image on an app's tile must be reasonably related to the content of the app. | Working with tiles, badges, and toast notifications (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app's tile must use a standard tile template. | Working with tiles, badges, and toast notifications (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app must not use its description, tiles, notifications, app bar, or the swipe-from-edge interactions to display ads. | Advertising Guidelines |
| [ ] | The app must fully support touch input, and fully support keyboard and mouse input. | Responding to user interaction (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Touch gestures and actions must match the Windows touch language. The app must not use touch gestures that are not in the Windows touch language. | Touch patterns |
| [ ] | The app must use the Windows 8 mouse language. | Responding to mouse interactions (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Interactive UI elements must provide visual feedback. Non-interactive UI elements must not provide visual feedback. | Guidelines for visual feedback (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | The app must remain functional when the customer resizes the app to any size, down to the default minimum size. | Guidelines for resizing and Guidelines for resizing to narrow layouts |
| [ ] | In landscape orientation, the app’s functions must be fully accessible when the app’s display size is 1024 x 768. | Guidelines for scaling to screens |
| [ ] | The app must not programmatically close, or offer UI affordances to close it. Windows 8 Process Lifetime Management closes Windows Store apps automatically. | Guidelines for app suspend and resume |
| [ ] | The app must suspend and resume to a reasonable state. | Guidelines for app suspend and resume |
| [ ] | If the app implements a bottom app bar, that bar must show up with a bottom-up swipe. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | If the app implements a navigation bar, that bar must show up with a top-down swipe. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app must respect system settings for notifications and remain functional when they are disabled. | Working with tiles, badges, and toast notifications (JavaScript and HTML or C#/VB/C++ and XAML) |
Highly recommended
We strongly recommend that your app follows the guidelines in this section. Each of these guidelines contributes to creating a well-designed app.
| Check | Description | Guidance |
|---|---|---|
| App Goals | ||
| [ ] | The app must have clear user experience goals and a clear ‘best at’ statement. | Planning Windows Store apps |
| [ ] | The app main page or hub page must be more than an embedded website. | Planning Windows Store apps Navigation patterns |
| Layout and alignment | ||
| [ ] | To organize content, the app must use alignment, typography, and white space consistently on all pages and views. | Laying out an app page Guidelines for typography |
| [ ] | The app must not use chrome (lines, boxes, and other UI elements) as the primary means of organizing content. | Laying out an app page Design case study: Website to Windows Store app |
| [ ] | If the app has a hub page, that page must not be primarily a menu to other pages of the app. It must contain useful content. | Navigation patterns |
| Grid | ||
| [ ] | UI elements must align to the grid. | Laying out an app page |
| Silhouette | ||
| [ ] | Title of the app must be placed consistently on all pages. | Laying out an app page |
| [ ] | Margins must be consistent on all pages. | Laying out an app page |
| [ ] | If the app has a fluid layout, the left margin must be at least 120px. | Laying out an app page |
| [ ] | The bottom margin must be at least 50px. | Laying out an app page |
| Panning and scrolling | ||
| [ ] | On a horizontally panning hub or main page, a vertically scrolling list must use snap points. | Guidelines for panning (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | On a vertically panning hub or main page, a horizontally scrolling list must use snap points. | Guidelines for panning (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | A page must not pan both vertically and horizontally unless the content requires freeform panning. | Guidelines for panning (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | If a page is scrollable, it must provide panning indicators. | Guidelines for panning (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | A horizontally panning page must not contain multiple vertically panning lists. | Guidelines for panning (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | A vertically panning page must not contain multiple horizontally panning lists. | Guidelines for panning (JavaScript and HTMLor C#/VB/C++ and XAML) |
| Typography | ||
| [ ] | The app must use a fixed set of type sizes and weights (type ramp). | Guidelines for typography Guidelines for fonts |
| [ ] | Fonts and font hierarchy must be consistent across pages. | Guidelines for typography Guidelines for fonts |
| [ ] | Casing and capitalization must be consistent. | Guidelines for typography |
| [ ] | The app must not contain spelling mistakes. | Guidelines for typography |
| [ ] | The app must not contain truncated text. | Guidelines for typography |
| Hosted web content | ||
| [ ] | The app must not contain hosted web content in an <iframe> on the hub page. | Quickstart: Using single-page navigation |
| If the app contains hosted web content in an <iframe>, it must provide a way to navigate back to the app. | Quickstart: Using single-page navigation | |
| [ ] | Web pages that are not direct app content must open in an external browser. | Guidelines and checklist for links |
| [ ] | Hosted web content must be aligned with the app silhouette. | Laying out an app page |
| Branding | ||
| [ ] | The app must have a splash screen image (620x320 pixels). | Guidelines and checklist for splash screens |
| [ ] | The splash screen must not include advertisements. | Guidelines and checklist for splash screens |
| [ ] | The splash screen must not contain essential app information, such as information about the app or help. | Guidelines and checklist for splash screens |
| [ ] | The transition between the splash screen and the first view of the app must not display a blank screen. | Guidelines and checklist for splash screens |
| [ ] | A logo must not prevent correct placement or alignment of the page title, and must not interfere with other content. | Branding |
| [ ] | The app must not reference non-Windows platforms in any branding or other app elements. | Branding |
| [ ] | Background images must not distract from or interfere with scanning and reading content. | Branding |
| App bars | ||
| [ ] | The bottom app bar must not include navigation, only commands. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The navigation bar must not include commands, only navigation. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app bars must not duplicate actions that are in charms. The only exception is print, which can be in the bottom app bar. | |
| [ ] | The app bars must close when the user taps the page or swipes from the bottom or top edge. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | When a user swipes to select an item, the app bar must open to show actions that are available for the selected item. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app must not have more than one bottom app bar visible at the same time. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Contextual commands must be placed on the left side of the bottom app bar (or right side for right-to-left languages). | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Text on app bar buttons must be center justified. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Commands must not be duplicated in the app bars. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Commands that are shared across pages must be placed as close to the same location in the app bar as possible. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app must not use an existing glyph for a new purpose. If no icon exists for the action or command, create one. | WinJS.UI.AppBarIcon AppBar button style images |
| Flyouts | ||
| [ ] | When a user changes something in a flyout, the content must update instantly to reflect the changes. | Guidelines and checklist for flyouts |
| [ ] | The app must not use modal dialogs for informational or contextual UI. Use flyouts for information and use context menus for contextual UI. | Laying out your UI (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | A flyout must close when the user taps the page or must have a close or cancel command. | Guidelines and checklist for flyouts |
| [ ] | A flyout must be placed near the associated app bar button. | Guidelines and checklist for flyouts |
| [ ] | A flyout must not obscure the command that opened it. | Guidelines and checklist for flyouts |
| [ ] | Flyouts must not have shadows or other elements that create a raised or 3D effect. Visuals in Windows are flat, not raised. | Guidelines and checklist for flyouts |
| [ ] | If a flyout includes navigation, it must include a back button. For example, the Settings pane allows a user to navigate to Settings flyouts, such as About and Feedback. These Settings flyouts include a back button to navigate back to the Settings pane. | Guidelines and checklist for flyouts |
| [ ] | A flyout that is positioned along the edge of the device must not interfere with edge swipes | Guidelines and checklist for flyouts |
| Context menus | ||
| [ ] | Objects that you can swipe to select directly must not have a context menu. | Guidelines and checklist for context menus |
| [ ] | Commands must not be duplicated in the app bar and in context menus. | Guidelines and checklist for context menus |
| Message dialogs | ||
| [ ] | Error messages must not contain stack traces or debug information. | Guidelines and checklist for message dialogs |
| [ ] | Error messages or confirmation questions that display in dialogs must apply to the whole app. | Guidelines and checklist for message dialogs Laying out your UI (JavaScript and HTML or C#/VB/C++ and XAML) |
| Sorting and filtering | ||
| [ ] | Filters that open from the app bar must use a flyout. | Navigation patterns |
| [ ] | Sort and filter flyouts must be placed near the associated app bar button. | Navigation patterns Guidelines and checklist for flyouts |
| [ ] | Sort and filter flyouts must close when the user taps the page. | Guidelines and checklist for flyouts |
| [ ] | The sort or filter options must be placed in a drop-down list if the sorting and filtering UI are on the canvas, and the app sorts or filters by more than one criterion. | Navigation patterns Guidelines and checklist for flyouts |
| [ ] | The app must not use sorting or filtering for navigation, for example, to mimic tabs. Instead, use sorting and filtering to allow users to quickly refine views of data. | Navigation patterns |
| Controls | ||
| [ ] | The app must allow direct manipulation instead of having separate edit or rearrange modes. | Commanding design Design case study: iPad to Windows Store app |
| [ ] | The app must not have custom actions or gestures to select items to edit or rearrange. | Guidelines for cross-slide |
| [ ] | The check mark on an item must be used only to indicate that the item is selected. | Guidelines for cross-slide |
| [ ] | If the user can select an item, there must be one or more commands associated with the selected item. | Guidelines for cross-slide Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Commands that are required for the user to progress must be placed on the canvas. | Laying out your UI (JavaScript and HTML or C#/VB/C++ and XAML) |
| Navigation | ||
| [ ] | The app must not have navigation controls on the canvas or page area, or in the bottom app bar. Navigation controls must be in the navigation bar.
Note The back button is an exception and can be on the canvas. |
Navigation patterns |
| [ ] | The app must not use tabs on the canvas for navigation. | Design case study: Website to Windows Store app |
| [ ] | Section or detail headers must open the supporting section or detail page. | Navigation patterns |
| [ ] | Section headers must have visible and actionable UI to show more content, such as a chevron indicator or the text, "View all <x>" | Navigation patterns |
| [ ] | The back button must be placed in the top left corner of the page or in the left of the navigation bar. For right-to-left languages, place the back button in the top right corner of the page or in the right of the navigation bar. | Navigation patterns |
| [ ] | The app must not have a disabled back button on the page or in the navigation bar. | Navigation patterns |
| Semantic zoom | ||
| [ ] | Semantic zoom must not be used to navigate to a different page in the app. You use semantic zoom to navigate to a different position on the same page. | Guidelines for semantic zoom (JavaScript and HTMLor C#/VB/C++ and XAML) Guidelines and checklist for semantic zoom controls (C#/VB/C++ and XAML) |
| [ ] | If the current view contains more than eight pages of content, you must use semantic zoom. | Guidelines for semantic zoom (JavaScript and HTMLor C#/VB/C++ and XAML) |
| Touch gestures | ||
| [ ] | UI elements, controls, and other parts of the app must not interfere with Windows edge gestures or the UI associated with Windows edge gestures. | Guidelines for common user interactions (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | If an item does not have a selected state, it must not implement the swipe to select gesture. | Guidelines for cross-slide |
| [ ] | A UI element must not have more than one command associated with it. More than one command on a single UI element causes ambiguity for touch gestures. | Guidelines for common user interactions |
| [ ] | Touch gestures must not overlap. The app must not have a scrollable map control, toggle switch, slider, or other control inside a scrollable viewer that interferes with panning or scrolling. | Guidelines for common user interactions |
| Touch targets | ||
| [ ] | Touch interactions must give the user feedback. | Touch patterns |
| [ ] | If an item is not actionable, it must not give the user touch feedback. | Touch patterns |
| [ ] | The app must not commit on touch down. Interactions must be reversible. | Touch patterns |
| [ ] | If the user drags off an item, the touch action must be cancelled. | Touch patterns |
| [ ] | Touch targets must be 5mm or larger. | Guidelines for targeting (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | The app must have at least 2 subunits (10 pixels) between touch targets. | Guidelines for targeting |
| Text input | ||
| [ ] | The app must use the Windows soft keyboard or an associated input method editor (IME). It must not use a custom soft keyboard. | Guidelines and checklist for IME development Guidelines for touch keyboard and handwriting panel |
| [ ] | The soft keyboard must not cover controls that are required to complete the text entry scenario. For example, the soft keyboard for a user name or password text box must not obscure the sign-in button. | Guidelines for touch keyboard and handwriting panel |
| Animations | ||
| [ ] | The app must implement animations where needed. | Animating your UI (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | Custom animations must not degrade performance or negatively impact the user experience. | Animating |
| [ ] | Animations and transitions must not have poor performance. For example, the user must not notice redrawing of tiles. | Animating Make animations smooth |
| Screen sizes and orientations | ||
| [ ] | Apps with a fluid layout must reflow for larger screens. | Guidelines for layouts Guidelines for scaling to screens |
| [ ] | Apps must not show noticeable artifacts or degradation in image quality on large or high-pixel density displays. | Guidelines for scaling to screens Guidelines for scaling to pixel density |
| [ ] | Apps must support portrait orientation of devices and monitors. Apps must support resizing in which the app is taller than it is wide. | Guidelines for resizing |
| [ ] | The app must maintain context and state when the user resizes the app. | Guidelines for resizing |
| [ ] | The app must be fully functional down to the default minimum size. If the app supports a minimum size that is smaller than the default, it should keep as much functionality as possible at the minimum size. | Guidelines for resizing Guidelines for resizing to narrow layouts |
| [ ] | The app layout and all controls must scale appropriately when the user resizes the app. The UI and controls must be usable in any size window. | Guidelines for resizing |
| [ ] | If the app supports widths from 320-499 pixels, the app must switch to a narrow, vertical view for narrow widths. Switch to panning vertically and use smaller margins, header, back button, and transition animation offsets. | Guidelines for resizing to narrow layouts |
| [ ] | The app must not programmatically change size. The user can resize the app at any time. | Guidelines for resizing to narrow layouts |
| [ ] | The app must not switch to a different part of the app when the window size changes. | Guidelines for resizing to narrow layouts |
| Contracts and charms | ||
| [ ] | The app must not duplicate the Settings, Share, or Devices charms on the app canvas or in the app bar. | Commanding patterns |
| [ ] | The app must support using the charms when it is at any size, orientation, or position on the screen. Charms apply to the last app the user used. | Guidelines for resizing to narrow layouts |
| Search contract and charm | ||
| [ ] | The app must not use the Search contract for find-in-page. Place find-in-page controls in the app bar. | Guidelines and checklist for find-in-page (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | If the app has a search control on the canvas, it must open the search contract. | Guidelines and checklist for search |
| Share contract and charm | ||
| [ ] | If sharing is implemented, it must be through the Share charm. | Guidelines for sharing content |
| [ ] | The app must display the correct message if it implements the Share charm but there is no shareable content in the current context. | Guidelines for sharing content |
| Settings contract and charm | ||
| [ ] | App settings, including configuration, options, and account management, must be implemented through the Settings charm, not on app pages or custom flyouts. | Guidelines for app settings |
| [ ] | About, Privacy statement, Terms of use, Help, and Feedback pages must be implemented through the Settings charm. | Guidelines for app settings |
| [ ] | The app must use controls consistently in the Settings pane. | Guidelines for app settings |
| [ ] | The Settings pane must close when the user taps the app. | Guidelines for app settings |
| [ ] | The Settings pane must have a back button. | Guidelines for app settings |
| [ ] | The Settings flyout must fit within the current width of the app. | Guidelines for resizing to narrow layouts |
| File picker | ||
| [ ] | The app must use the file picker to open, save, or access files. | Guidelines for file pickers Guidelines and checklist for file picker contracts |
| [ ] | The app must not use the file picker to explore or consume content. | Guidelines for file pickers |
| Tiles | ||
| [ ] | If the app uses a wide tile, it must have live content for the tile. | Guidelines and checklist for tiles and badges |
| [ ] | The app tile colors, fonts, and icons must be consistent with those of the app. | Guidelines and checklist for tiles and badges |
| [ ] | The app icon or logo on the tile must be high quality and must not show noticeable artifacts. | Guidelines and checklist for tiles and badges |
| [ ] | Text on the tile must be spelled correctly. | Guidelines and checklist for tiles and badges |
| [ ] | A secondary tile must not link to static content. | Guidelines and checklist for secondary tiles |
| [ ] | A secondary tile must not be a command button that allows the user to interact with the app. | Guidelines and checklist for secondary tiles |
| [ ] | A secondary tile must navigate directly to the related content. It must not open the home page of the app. | Guidelines and checklist for secondary tiles |
| [ ] | The app must not use secondary tiles to display ads. | Guidelines and checklist for secondary tiles |
| Toast notifications | ||
| [ ] | The app must not use toast notifications for error messages. | Guidelines and checklist for toast notifications |
| [ ] | Toast notifications must be actionable and must navigate to the app when the user taps them. | Guidelines and checklist for toast notifications |
| [ ] | The app must not use toast notifications for ads. | Guidelines and checklist for toast notifications |
| [ ] | The app must not use toast notifications for minor changes. | Guidelines and checklist for toast notifications |
| Roaming | ||
| [ ] | Roamed data must roam consistently and accurately. For example, data must not roam to one device but not another. | Guidelines for roaming app data |
| Account management | ||
| [ ] | Account management features must be implemented from the Settings charm. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The user must be able to log out from the Settings charm. | Guidelines and checklist for login controls |
| [ ] | An entry point to log in from the app must open the Settings charm. (Exception: web authentication) | Guidelines and checklist for login controls |
| [ ] | If the app does not require authentication, it must not display login controls. | Guidelines and checklist for login controls |
| [ ] | A standard web authentication dialog must be used where appropriate. | Web authentication broker |
Recommended
The guidelines in this section improve the user's experience of the app.
| Check | Description | Guidance |
|---|---|---|
| Layout and alignment | ||
| [ ] | Content should be left aligned (right aligned for right-to-left languages) on all app pages, in all views. | Guidelines for typography |
| [ ] | The app's hub or main page should include visual variation. | Navigation patterns |
| Silhouette | ||
| [ ] | Columns should be at least 560 pixels (28 units). | Laying out an app page |
| [ ] | If the app uses the standard silhouette, it should adhere to the following guidance:
|
Laying out an app page |
| Panning and scrolling | ||
| [ ] | On a horizontally panning page, content must scroll to the left edge. Content must not stop scrolling at the left margin. | Guidelines for panning (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | All areas of a page should respond to panning and scrolling. | Guidelines for panning |
| Typography | ||
| [ ] | The type ramp for the app should not have more than five type sizes. | Guidelines for typography |
| [ ] | The app should use sentence casing. | Guidelines for typography |
| Branding | ||
| [ ] | If the app has an extended splash screen, it should be similar to the initial splash screen. | Guidelines and checklist for splash screens |
| [ ] | The app should include splash screen assets to support 1.4x (868x420 pixels) and 1.8x (1116x540 pixels) scaling. | Guidelines and checklist for splash screens |
| [ ] | If the splash screen is visible for more than 7 seconds, it should provide a visual cue that the user should wait for the app to load. | Guidelines and checklist for splash screens |
| [ ] | The app should have a logo on the hub page. | Branding |
| App bars | ||
| [ ] | The app bar should not include previous and next commands. Instead, the app should include a flip control on the canvas. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) Adding FlipView controls (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app should not have a blank app bar. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app bars should not duplicate actions that are in charms. | Commanding patterns |
| Context menus | ||
| [ ] | Context menus should be placed near the target object | Guidelines and checklist for context menus |
| Sorting and filtering | ||
| [ ] | Sort and filter commands that are essential to the app scenario should be placed on the canvas. Sort and filter commands that are not essential should be placed in the app bar. | Navigation patterns |
| [ ] | The app should have no more than one sort button and one filter button per app bar. | Guidelines and checklist for app bars (JavaScript and HTML or C#/VB/C++ and XAML) |
| Navigation | ||
| [ ] | If the app has more than four levels of hierarchy, it should use a header drop-down list or the navigation bar to navigate to different sections. | Navigation patterns |
| [ ] | You should implement the back button as a back stack so that it behaves like a browser history button. | Navigation patterns |
| [ ] | The back button should not be displayed over full-screen video. It should fade out or be placed in the navigation bar. | Audio and video performance Optimize media resources |
| Semantic zoom | ||
| [ ] | If the current view contains more than five pages of content, you should use semantic zoom. | Guidelines for semantic zoom (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | The semantic zoom view should include additional relevant information. | Guidelines for semantic zoom (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | When the user zooms out, the app should have a standard left margin. | Guidelines for semantic zoom (JavaScript and HTMLor C#/VB/C++ and XAML) |
| Touch | ||
| [ ] | Touch targets for actions in which accuracy is important, like delete and close, should be 9 mm or larger. | Touch patterns |
| [ ] | All touch targets should be 7 mm or larger. | Touch patterns |
| Keyboard and mouse | ||
| [ ] | The app should support navigation and selection by using a keyboard. | Guidelines for common user interactions (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | Content containers in the app, such as lists and grids, should support mouse wheel scrolling. | Mouse interactions (JavaScript and HTML or C#/VB/C++ and XAML) |
| [ ] | The app should support mouse hover feedback. | Mouse interactions (JavaScript and HTML or C#/VB/C++ and XAML) |
| Animations | ||
| [ ] | Animations should not inhibit natural progress through the app. | Using animations in your app (JavaScript and HTMLor C#/VB/C++ and XAML) |
| [ ] | Animations should not distract the user. | Using animations in your app (JavaScript and HTMLor C#/VB/C++ and XAML) |
| Screen sizes and orientations | ||
| [ ] | Apps that have a fixed layout should be centered on all screen sizes and pixel densities. | Guidelines for scaling to screens |
| [ ] | Transitions between orientations should be fluid. They should not show redraw operations. | Guidelines for resizing |
| [ ] | Transitions when resizing should be fluid. They should not show redraw operations. | Guidelines for resizing |
| Search contract and charm | ||
| [ ] | If the app has searchable content, it should implement the Search contract. | Guidelines and checklist for search |
| [ ] | If no search results are returned, the app should provide a meaningful message to the user. | Guidelines and checklist for search |
| [ ] | The app should display search criteria with the search results. | Guidelines and checklist for search |
| [ ] | If the app implements the Search contract, it should enable type to search. | Guidelines and checklist for search |
| Share contract and charm | ||
| [ ] | An app with shareable content should implement the Share source contract. | Guidelines for sharing content |
| [ ] | An app that allows publishing, storing, or creating content should implement the Share target contract. | Guidelines for sharing content |
| Settings contract and charm | ||
| [ ] | Changes that the user makes in the Settings pane should be committed immediately. | Guidelines for app settings |
| [ ] | Any disabled control in the Settings pane should have a descriptive message that explains why it is disabled. | Guidelines for app settings |
| [ ] | The Settings flyout should be either narrow (346 pixels) or wide (646 pixels). | Guidelines for app settings |
| File picker | ||
| [ ] | If the app provides a save location, it should implement the File Open Picker contract. | Guidelines and checklist for file picker contracts |
| Tiles | ||
| [ ] | If an app has dynamic content, it should implement a live tile. | Guidelines and checklist for tiles and badges |
| [ ] | The tile should not duplicate the name or logo. | Guidelines and checklist for tiles and badges |
| [ ] | Secondary tiles that are wide should have live content. | Guidelines and checklist for secondary tiles |
| Toast notifications | ||
| [ ] | When the app is visible on the screen, toasts should not be displayed. | Guidelines and checklist for toast notifications |
| [ ] | Toast notifications should not have an 'x' icon to close the notification. | Guidelines and checklist for toast notifications |
| Roaming | ||
| [ ] | The app should roam suitable data, such as app settings and preferences, activity history, favorites, and user-defined lists. | Guidelines for roaming app data |
Related topics
Windows Store app UX test cases
Build date: 9/16/2013