Principles
Time your website with
WebWait - from the creator of AjaxPatterns.orgFrom Ajax Patterns
(Difference between revisions)
| Revision as of 11:57, 15 May 2005 Mahemoff (Talk | contribs) ← Previous diff |
Revision as of 11:59, 15 May 2005 Mahemoff (Talk | contribs) Next diff → |
||
| Line 3: | Line 3: | ||
| * Avoid distractions such as gratuitous animations so that the user can focus on the task at hand. | * Avoid distractions such as gratuitous animations so that the user can focus on the task at hand. | ||
| * Stick with AJAX wherever possible - just say no to entire page downloads so that the user’s experience is consistent. | * Stick with AJAX wherever possible - just say no to entire page downloads so that the user’s experience is consistent. | ||
| - | * Adopt AJAX for usability, not just to illustrate you’re hip to where it’s at so that the user is engaged, and not immediately driven away by your nod to website splash screens, <blink> tags, popup ads, and other usability disasters of websites which have gone to a place you don’t want to be. | + | * Adopt AJAX for usability, not just to strut your stuff, so that the user is engaged, and not immediately driven away by your nod to website splash screens, <blink> tags, popup ads, and other usability disasters of websites which have gone to a place you don’t want to be. |
| Some (and eventually all?) of these principles above inform the AJAX patterns. The patterns are about trading off among the principles, and also about resolving conflict between the needs of usability and other practical constraints, such as ease-of-development. | Some (and eventually all?) of these principles above inform the AJAX patterns. The patterns are about trading off among the principles, and also about resolving conflict between the needs of usability and other practical constraints, such as ease-of-development. | ||
Revision as of 11:59, 15 May 2005
- Minimise traffic between browser and server so that the user feels the application is responsive.
- Be clear on the interaction mode being used - regular HTML versus AJAX versus desktop application so that the user can predict what will happen next .. no * While avoiding confusion, borrow from conventions of HTML and desktop applications so that the user can rapidly learn how to use your application.
- Avoid distractions such as gratuitous animations so that the user can focus on the task at hand.
- Stick with AJAX wherever possible - just say no to entire page downloads so that the user’s experience is consistent.
- Adopt AJAX for usability, not just to strut your stuff, so that the user is engaged, and not immediately driven away by your nod to website splash screens, <blink> tags, popup ads, and other usability disasters of websites which have gone to a place you don’t want to be.
Some (and eventually all?) of these principles above inform the AJAX patterns. The patterns are about trading off among the principles, and also about resolving conflict between the needs of usability and other practical constraints, such as ease-of-development.
