Chapter 1

� Incorporate folders to divide data into user definable sets.
14.4.4 Standard Menu Items
UIQ defines a set of standard items that appear on the Edit menu such as Cut, Copy, Paste,
Zoom and Preferences. Ifa Folders menu is used, the standard items are Business, Personal
and Unfiled, with slight variations depending on whether you are in a List view or a Detail
view.
Clearly, not all applications need to feature all these items on their menu lists. Equally
clearly, most applications have their own menus too. The UIQ Style Guide recommends you
provide your application-specific menu items within the Application menu.
14.4.5 Creating Dialogs
Dialogs are messages that prompt the user to respond. They always appear as wide as the
screen and can be categorized into information dialogs, setting dialogs, query dialogs,
notification dialogs, and process dialogs:
� Make sure you use the correct type of dialog for the purpose.
� Apply a dialog title with clear context.
� Use buttons such as Done, No/Yes, and Continue instead of OK.
� Keep the dialog layout as uncluttered as possible.
� Align control labels to the right and controls to the left.
� Make sure buttons are right justified and at the bottom of the dialog.
� Use multipage dialogs only when there's no other alternative and avoid adding more
tabs than will fit on the screen.
14.4.6 Considering Text Input
Handwriting recognition, in which pen gestures are interpreted as letters, numbers, or other
characters and sent to the application as text, is UIQ's main method for text input. Using a
virtual keyboard is the other alternative.
� Handwriting should only be activated when the focus is on text control.
� Bear in mind that the virtual keyboard takes up screen space when activated and might
hide important features.
14.4.7 Providing Text and Messages
Providing concise wording and clear instructions on menus, dialogs, notifications, infoprints,
and other information messages is very important for the usability of your application.
� Use the standard vocabulary set by UIQ, its applications, and the style guide. Avoid
ambiguity and programmer-centric vocabulary ('show the hidden window'); instead use
user-centric vocabulary ('hide the game'). Take particular care over text that has to be
short – on buttons, for example. Make sure that yes/no questions can only have those
answers. Reassure the user: make it plain what the result of any action will be
� Remember that the pointer is a pen, not a mouse. Use pen-centric metaphors: use
single-tap rather than double-click, and avoid drag- and-drop
� Avoid unnecessary jargon and use only standard computer vocabulary
� Use complete sentences where possible, rather than truncating them
� Be consistent with terms – use the same terms for the same things, regardless of
whether you use standard UIQ terms or your own
� Don't end error messages with an exclamation mark or infoprints with a full stop