×

Discussion Board

Results 1 to 2 of 2
  1. #1
    Registered User
    Join Date
    Mar 2003
    Posts
    34

    General UI desing principles with the 9210

    What are the general UI desing principles with the 9210?

  2. #2
    Regular Contributor
    Join Date
    Mar 2003
    Posts
    157

    RE: General UI desing principles with the 9210

    - Applications should interact with the user
    - User key presses should be acknowledged in some way. The application should always react to the key presses.

    - The UI should be as flexible as possible: if there are two ways to perform an action, you should allow the user to choose his or her own favourite way.

    - All of the application functionality should be visible at all times
    - Indicate commands and controls that are available
    - If a command cannot be executed at one point for some reason, then the command should be dimmed. Sometimes, when the user selects a dimmed command, an Information Banner indicating ''Command not available'' can be displayed.
    - If a command cannot be executed at any time, it should not be visible in the UI at all.

    - The UI should be consistent across different applications and across other devices which operate on the same platform. This means for example:
    - Common dialogs
    - Common menu structures
    - Common shortcuts
    - Common CBA functionality
    - Common terminology
    - Common graphics
    - Common task flow, i.e. carrying out the same type of task should be similar across applications within the UI

    - Minimise the UI
    - Less work for the implementer and less work for the user. 'Make it simple!'
    - Hide the complexity, if complexity is needed at all
    - Common actions should be available with as few key presses and hand movements as possible

    - Do not frustrate the power users: Provide shortcuts

    - Let the user have control: do not over-automate

    - Provide feedback

    - Use Notes and/or audio feedback when it is not obvious what has happened

    - Avoid ''flicker'' when an application is redrawn; no part of the UI should flicker when the display is updated

    - Speak the user's language

    - Provide an undo functionality, that is, make things reversible

    - Allow swapping from one application to another. A given application must not block other activity

    - Allow cancellation of the operation at every stage

    - If you develop an application that is not going to be localised, make sure that you create all strings yourself. Do not take them from the system. This is because the operating system that your application runs on may well be in another language. The communicator is localised. Mixed language versions are not good from the point of view of style, nor are they user friendly.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×