|
⇤ ← Revision 1 as of 2009-03-24 16:14:51
Size: 1377
Comment:
|
Size: 1379
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DEV/versions/7962633 | #pragma page-filename DEV/versions/7962636 |
| Line 3: | Line 3: |
| Consistency in user interfaces lets users make less errors and they feel more secure in what they do.<<BR>> | Consistency in user interfaces lets users make less errors and they feel more secure in what they do. <<BR>> |
Global Requirements
Consistency in user interfaces lets users make less errors and they feel more secure in what they do.
In theory all clients should conform to the following requirements. In practice mileage depends on what the client technology gives.
Accessibility
If a client technology provides means to make the interface more accessible, they should be followed.
Design Patterns
Operating systems have design patterns that describe how things should look and how standard processes should work. If we develop a client for a system that provides such a catalog we should follow it. Users will honour the consistency, feel at home and will make less errors.
information architecture
navigation structure
messages and notifications
We should provide a set of MM3 specific help messages and notifications. Any client should use these, so users get a consistent experience - no matter which client.