×
Namespaces

Variants
Actions
(Difference between revisions)

Dialog usability

From Nokia Developer Wiki
Jump to: navigation, search
kiran10182 (Talk | contribs)
m (Internal link given)
SannaH (Talk | contribs)
Line 3: Line 3:
 
* Keep your terminology the same throughout the application.  
 
* Keep your terminology the same throughout the application.  
 
* Remember feedback! It’s important to tell the user when something is happening.
 
* Remember feedback! It’s important to tell the user when something is happening.
* Make informative error messages so the user knows what happened and what needs to be
+
* Make informative error messages so the user knows what happened and what needs to be done to recover (see [[Error message]] ).
* done to recover (see [[Error message]] ).
+
 
* Make sure the user has the opportunity to reverse from any situation with Back or Cancel, for example.
 
* Make sure the user has the opportunity to reverse from any situation with Back or Cancel, for example.
 
* Keep the dialogs simple so that the user’s memory won’t be loaded with too much information.
 
* Keep the dialogs simple so that the user’s memory won’t be loaded with too much information.
  
 
[[Category:Development Process]][[Category:Usability]]
 
[[Category:Development Process]][[Category:Usability]]

Revision as of 09:28, 6 May 2009

Some things to remember when designing dialogs:

  • Be consistent.
  • Keep your terminology the same throughout the application.
  • Remember feedback! It’s important to tell the user when something is happening.
  • Make informative error messages so the user knows what happened and what needs to be done to recover (see Error message ).
  • Make sure the user has the opportunity to reverse from any situation with Back or Cancel, for example.
  • Keep the dialogs simple so that the user’s memory won’t be loaded with too much information.
172 page views in the last 30 days.
×