Wednesday, December 26, 2007

AJAX Usability Checklist

Ajax usability checklist ...

"This Ajax Usability Checklist is a bonus guide that accompanies my AJAX Usability Seminar, I am offering it in the form of this post as a bonus for readers- thanks for your support!

The Web is changing fast. New standards are emerging, new approaches to coding such as Scriptaculous, AJAX, Ruby, Flash/Flex, Silverlight and others are creating a leap-frog situation where many new websites, web apps and portals are implementing next year's User Interface elements.

Yet, when it comes to implementing the new interface techniques AJAX offers, we need to be mindful of how AJAX can improve the specifics of the user experience.

Two simple guidelines for AJAX Usability:

1) If the user has to ”play” with the interface control too much it is probably used inappropriately.

2) If the interface control does not follow the user’s task, it is probably used gratuitously.

1. When and where to use AJAX

a) When presenting complex features or functionality

b) When building a data set for the user

c) When presenting depth of information

d) To correct or intelligently help the user

a) When presenting complex features or functionality

EXAMPLE: offers a complex ring configurator with advanced filtering and sorting functionality.

An AJAX interface allows users to hover over ring specifications.

Sliders help narrow the selection.

Note: Top to bottom sliders are novel and should be tested since they are less familiar UI elements on the Web."    (Continued via Demystifying Usability)    [Usability Resources]


Anonymous Anonymous said...

I would like to draw your attention to another alternative which is a paradigm shift for AJAX/ Silverlight front ends. One should be aware that I am not, and do not pretend to be objective, never the less I believe that one can judge for himself. Visual WebGui is an open source rapid application development framework for graphic user interfaces of web applications, Silverlight or standard browser at developer/ user's choice. VWG replaces the paradigms of ASP.NET in both design-time and run-time which were designed for developing sites, with WinForms methodologies, which were designed for developing applications. Thus enabling designer that was designed for application interfaces instead of a word documents (ASP.NET designer). This provides the developer with an extremely efficient way to design interfaces using drag and drop instead of hand coding HTML. Visual WebGui is an AJAX / Silverlight frame work that doesn’t expose logic, data or open services on client requests and therefore is not as vulnerable as common AJAX solution. VWG presentation layer is de-coupled and that is why it becomes developer choice Silverlight or standard browser.
NO!!! Visual Webgui is not!!
Not a component library – It is a complete revised approach to developing web applications.

not a JavaScript generator – It runs on the server controlling the browser using a small static JavaScript kernel.

Not a closed / locked-in framework – It has many extensibility features, which allow integration of legacy resources (ASP.NET or DHTML resources) and the development of custom controls and behaviors.
Worth a look at,

11:38 PM  

Post a Comment

<< Home

<< Home