Recently I read an articile from Nokia Forums. Its really a must read article for every web application desginers. Here for you..
Provide a clear navigation model
Core features should be available from the main view.
Limit the number of menu choices – make them context specific.
Navigation model should be focused on the user’s main tasks.
Advanced functionality should be hidden from novice users.
Use familiar language
Use terms that are familiar to the user and relates to the users’ tasks and goals.
Terminology should be consistent with the Series 60 UI style.
Localize: target users’ native language should be used.
Hide the complexity of connectivity
Short network coverage problems should not cause loss of users' work or stop them from working.
Connection status should be displayed clearly.
Synchronization should be automatic but under user control.
Provide useful feedback
Let the user know immediately if an action was successful or not.
If processing takes more than 0.5 seconds, indicate that something is happening, for example, with a progress bar.
Be consistent with controls
Minimize errors and the need for learning by using softkeys according to the Series 60 UI style.
Build shortcuts for advanced users, use shortcuts similar to other applications.
Make sure that the most important actions are also available in the Options menu.
Provide a simple Options menu
Navigation key default action(s) should also be available in an Options menu.
Sort items in the Options menu according to the Series 60 UI Style Guide.
Main actions should be available without scrolling.
Use tabs wisely
The most essential functionality should be provided in the first tab. Underlying tabs can be used to hide advanced functionality.
If more than five tabs are needed, use a list for accessing the tabs (see the Settings application).
Text is preferable to icons in tab titles.
Make information entry easy
Instead of text entry, prefer alternative forms of information entry, such as selecting from a list or capturing images.
Offer reasonable default values.
Focus should always be easily movable with the arrow keys.
Display information clearly
Display the most relevant information first.
Essential information should not be displayed with icons only.
Use colors and symbols for highlighting and grouping items.
Provide help
Context-sensitive help should be provided in the application.
Give step-by-step guidance when the user is accomplishing difficult tasks.
More detailed help should be provided on a Web site or in the user guide.
Thursday, November 29, 2007
Top Ten Problems with Web Application Usability - by Frank Spillers
Here are some of the top recurring web application usability issues we found from some recent usability research conducted on web applications.
1. Forms that do not auto-populate. Form fields are a typical design element used in registering or searching, for example. (To maximize usability, forms scripting should be programmed correctly to reduce user workload). Forms forcing users to enter redundant information across multiple screens, adds extra effort and may increase process frustration. Forms should also preserve user data across screens in order to adjust data with "Back button" actions.
2. Controls missing consistent logic. Again, scripting forms correctly is important. Dropdown menus that auto-populate a field, such as State/Province, on one page and then do not have the auto-populate function with the same functionality found elsewhere, keep users on their toes (and undermine any perceived usefulness gained from auto-populating).
3. Information requested but not justified. Unnecessary information is perceived as intrusive and annoying, unless rewarded by a motivating gain. Personal information requested or an excessive amount of personal information collected bogs down the process and may be the source of "conversion leakage".
4. Making analysis difficult. Web applications typically provide three main actions: Registration, Add or Create new Data, Review or Change Data.Tables that are hard to interpret or read, interaction that is nested between screens and all "data" and "no information" can reduce the usefulness of the overall application.
5. Failing to offer useful Help. Web applications that require intense studying or involve complex rules or interpretation tend to bog down ease of understanding. Offer a "What is this?" link or describe the purpose of a form in the right hand area (see Yahoo Briefcase sign up process).
6. Forcing lengthy registrations. Registration that requires 8-10 steps will lead to poor registration conversion. Legal agreements do not have to take up multiple pages or multiple pages of text to read.
7. Having unwarned time outs. Ending sessions after 15 minutes without any warning can lead to confusion, anger and annoyance. Offer time out warnings (pop ups).
8. Unhelpful login. Log-in seems to be one of those "necessary evil" on the web. Log-ins that require numeric characters without notice or do not show examples of "username" at log-in are frustrating and can reduce the reuse of a web based application. This goes to say that "forgot your password?" should include any and all log-in screens.
9. Configuring settings and preferences. Forcing users to configure access to a web application without explaining the process involved can add extra effort and increase perceived complexity of the web application.
10. Misrepresenting the user's task with your features. Getting users to jump through hoops to get their work done based on the way you've built the application, not how users want and need it, is probably the single biggest opportunity for improvement.
Note: Specific examples above are taken from research based on Experience Dynamics expert Usability Reviews of web application dashboards including two popular search engine ad applications, two popular web analytics web applications and several email marketing applications.
1. Forms that do not auto-populate. Form fields are a typical design element used in registering or searching, for example. (To maximize usability, forms scripting should be programmed correctly to reduce user workload). Forms forcing users to enter redundant information across multiple screens, adds extra effort and may increase process frustration. Forms should also preserve user data across screens in order to adjust data with "Back button" actions.
2. Controls missing consistent logic. Again, scripting forms correctly is important. Dropdown menus that auto-populate a field, such as State/Province, on one page and then do not have the auto-populate function with the same functionality found elsewhere, keep users on their toes (and undermine any perceived usefulness gained from auto-populating).
3. Information requested but not justified. Unnecessary information is perceived as intrusive and annoying, unless rewarded by a motivating gain. Personal information requested or an excessive amount of personal information collected bogs down the process and may be the source of "conversion leakage".
4. Making analysis difficult. Web applications typically provide three main actions: Registration, Add or Create new Data, Review or Change Data.Tables that are hard to interpret or read, interaction that is nested between screens and all "data" and "no information" can reduce the usefulness of the overall application.
5. Failing to offer useful Help. Web applications that require intense studying or involve complex rules or interpretation tend to bog down ease of understanding. Offer a "What is this?" link or describe the purpose of a form in the right hand area (see Yahoo Briefcase sign up process).
6. Forcing lengthy registrations. Registration that requires 8-10 steps will lead to poor registration conversion. Legal agreements do not have to take up multiple pages or multiple pages of text to read.
7. Having unwarned time outs. Ending sessions after 15 minutes without any warning can lead to confusion, anger and annoyance. Offer time out warnings (pop ups).
8. Unhelpful login. Log-in seems to be one of those "necessary evil" on the web. Log-ins that require numeric characters without notice or do not show examples of "username" at log-in are frustrating and can reduce the reuse of a web based application. This goes to say that "forgot your password?" should include any and all log-in screens.
9. Configuring settings and preferences. Forcing users to configure access to a web application without explaining the process involved can add extra effort and increase perceived complexity of the web application.
10. Misrepresenting the user's task with your features. Getting users to jump through hoops to get their work done based on the way you've built the application, not how users want and need it, is probably the single biggest opportunity for improvement.
Note: Specific examples above are taken from research based on Experience Dynamics expert Usability Reviews of web application dashboards including two popular search engine ad applications, two popular web analytics web applications and several email marketing applications.
Subscribe to:
Posts (Atom)