Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

(Difference between revisions)

Dialog usability

From Wiki
Jump to: navigation, search
SannaH (Talk | contribs)
(New page: 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 s...)
 
kiran10182 (Talk | contribs)
m (Internal link given)
Line 4: Line 4:
 
* 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 [[http://wiki.forum.nokia.com/index.php/Error_message 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 12:54, 28 November 2007

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.
238 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×