CS615
Spring 2012
UI Principles
Principles extracted from examples (first two classes, student answers
to hw questions).
-
Transparent.
If the UI is good you don't even notice it. That can mean several
things.
- Appropriate defaults
- Text/Icons identify actions well
- Works for both confident and anxious users
- Works for both new and experienced users
-
Clutter free.
-
Jargon free.
-
Fast.
-
Fault tolerant.
Never freeze, never lose previously entered information when returning
to a form.
-
Feedback.
Reward significant action with feedback (acknowledgements,
messages, prompts)
-
Not frustrating.
If she has a choice she'll abandon the task.
-
Help
should be available - and unnecessary.