Bureaucrats, emailconfirmed
1,221
edits
IFD:Course Interaction Design (view source)
Revision as of 13:47, 15 November 2010
, 15 November 2010→Standards and Consistency
| Line 361: | Line 361: | ||
So what is the way around this? Most importantly: design you product carefully and only include functionality that serves the users goals well. If there is no way around than you can use "progressive disclosure": The interface has some main functions that are always visible and some advanced functionality that is visible when the user demands it. Often this is done by displaying important stuff at the top and offering a button that shows the additional functions. Using this way there are no arbitrary changes nor a whole new order is introduced as the basic functions remain in place. | So what is the way around this? Most importantly: design you product carefully and only include functionality that serves the users goals well. If there is no way around than you can use "progressive disclosure": The interface has some main functions that are always visible and some advanced functionality that is visible when the user demands it. Often this is done by displaying important stuff at the top and offering a button that shows the additional functions. Using this way there are no arbitrary changes nor a whole new order is introduced as the basic functions remain in place. | ||
====Resources==== | |||
* [http://www.useit.com/alertbox/990822.html Do Interface Standards Stifle Design Creativity?] | |||
*Example Interface Guidelines by [http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html Apple] and [http://library.gnome.org/devel/hig-book/stable/ Gnome] | |||
===Visibility=== | ===Visibility=== | ||