Design Guidelines

The user interface guidelines for Windows Mobile 6 Professional and Windows Mobile 6 Classic assist you in developing Windows Mobile powered applications that provide a good user experience.

Accessibility and Ergonomic Guidelines

Outlines the guidelines for developing an accessible user interface.

Home and Today Screen Guidelines

Describes the information the user might want instant access to, and ways to display it when the component is selected.

Mobile Web Site Design Overview

Some general guidelines on how to optimize your Web site design for Internet Explorer Mobile.

Navigation Guidelines

Describes the various views (list view, summary view, and edit view). and provides recommendations for using them.

Screen Rotation Guidelines

Describes practical approaches you can take to create screen layouts that accommodate portrait, landscape, and square.

Soft Key and Menu Guidelines

Describes the role that Soft Keys play in the user interface, and how to properly implement them in your applications.

Usability Guidelines

Provides a checklist to help you confirm that your application's user interface meets usability requirements.

User Interface Control Guidelines

Provides guidelines for user interface (UI) controls.

User Interface Text Guidelines

Provides guidelines for designing user interface text.

Acronyms and Terminology Guidelines
8/28/2008

You can help users learn more quickly by using terminology that is clear, consistent, and familiar. Avoid jargon such as "screen real estate" and "reboot."

Note:

Translating jargon increases localization time and costs.

• 
  Confirm that the acronym isn't already being used to represent a different phrase or name.
  
• 
  To conserve user interface space, do not spell out acronyms.
  
• 
  Determine whether the acronym will be problematic in languages other than English.
  

Apply the following geopolitical guidelines to the user interface text:

• 
  Always use the term country/region instead of the word country.
  
• 
  Always use the term capital/major city instead of the word capital.
  
• 
  Be cautious when using an untranslated trademarked term from the United States because it might be interpreted as an offensive or otherwise undesirable term in another language.
  

• 
  Use terminology, punctuation, acronyms, and capitalization consistently.
  
• 
  Avoid idioms, jargon, colloquialisms, abbreviations, acronyms, and metaphors whenever possible.
  
• 
  Avoid long compound sentences with multiple nouns because they are difficult to translate.
  
• 
  Use descriptors wherever possible.
  
• 
  When using punctuation, take into account that other languages have different rules.
  
• 
  Localizing English text usually increases the length of the text, which may affect the layout of controls. As needed, use standard abbreviations and rephrase text to ensure that it fits on the screen.
  The following illustration shows the difference in text length when the same content is localized in three different languages.
  

English	German	Japanese

Follow these guidelines when you write error messages and informational text:

• 
  Identify the problem, indicate the cause if helpful, and provide a solution if possible.
  
• 
  Write phrases instead of complete sentences to conserve space. For example, write "Save using a different name" instead of "Save this document using a different file name."
  
• 
  Use title caps in the title bar of the message box and sentence caps in the message body text.
  Title caps rules specify that all words are capitalized with the exception of articles, coordinating conjunctions (and, but, for, not, or, so, and yet), and prepositions containing four or fewer letters.
  Sentence caps rules specify that only the first word and any proper nouns are capitalized.
  
• 
  Bold command names instead of using quotation marks.
  
• 
  When there may be a consequence of a user's action, preface the error message with the word "Warning." For example, write "Warning: If you synchronize now, duplicate items may appear in your Inbox."
  
• 
  Do not use exclamation points.
  
• 
  Do not write content that implies that applications can think or feel.
  
• 
  Avoid using the word please. Also, use the following alternative terms for abort, boot, and reboot.
  

Instead of	Use
Abort	End, quit, or stop
Boot	Start or switch on
Reboot	Start

The topics in this section provide guidelines for the design of user interface text. Because of the limited amount of screen space available on most Windows Mobile powered devices, it's extremely important minimize the amount of textual information displayed on the device. In addition, mobile professionals don't have a lot of time or desire to read large amounts of text to accomplish specific tasks. When writing user interface (UI) text for Windows Mobile powered devices, consider the following questions:

• 
  Is the user interface text clear, concise, and contextually relevant for the audience?
  
• 
  Does the text consistently follow the style, terminology, and tone and voice specified for the product?
  
• 
  Does the text follow localization and geopolitical guidelines?
  

When writing UI text for Windows Mobile powered devices, use the guidelines in the following checklist:

• 
  Use clear terminology.
  
• 
  Avoid technical jargon and colloquialisms.
  
• 
  Use as few words as possible without losing the meaning.
  
• 
  Use one term consistently for all concepts that have the same meaning.
  
• 
  Avoid negative and politically sensitive terms.
  
• 
  Write active sentences.
  
• 
  When writing instructional text, present the result before the required action. For example, "To begin importing contacts, click Next."
  
• 
  Allow for at least 30 percent text expansion for localization.
  
• 
  Follow the Mobile Devices Product Group capitalization and punctuation guidelines.
  
• 
  Make sure UI command labels match labels for the UI they open.
  
• 
  Write informative error messages.
  
• 
  Ask an editor to review all UI text.
  

The following table indicates the type of capitalization you should use for user interface (UI) controls.

Use the following checklist to confirm that an application user interface meets basic usability requirements:

• 
  Dialog boxes do not contain irrelevant information because it diminishes the visibility of relevant information.
  
• 
  Information appears in a logical order in the dialog box based on the functionality provided. The information is communicated using words and concepts that are familiar to a user. Consider the following to keep the user interface simple and focused:
  
  • 
    Place commands for critical features in a prominent area such as a menu.
    
  • 
    Place advanced and less-frequently used commands in a less prominent area such as a submenu or settings dialog.
    
  • 
    Avoid placing commands redundantly, with the exception of shortcut menu commands on Windows Mobile 6 Professional and Windows Mobile 6 Classic.
    
• 
  Instructions for using an application are visible or easily accessible whenever appropriate. Avoid complicated instructions.
  
• 
  When appropriate, the same user action is consistently used to complete the same application operation.
  
• 
  Consistency is applied to the visual presentation of information, placement of user interface elements, and format, capitalization, and punctuation of user interface text.
  Avoid visual noise in the user interface because it distracts users from completing tasks. Visual noise is created by misaligned controls or redundant borders of neighboring controls.
  
• 
  Appropriate feedback is provided to a user within a reasonable time.
  
• 
  Shortcuts for experienced users are provided for completing tasks.
  
• 
  Error messages are provided that concisely explain a problem and contain meaningful suggestions for resolving the problem. For more information, see Error and Informational Message Guidelines.
  
• 
  Whenever possible, the application design prevents errors from occurring.
  

The following table provides descriptions for user interface (UI) controls. Refer to the linked topics for guidelines and details for each UI control.