As more sites evolve to Web 2.0 we find that clients do not always understand what Ajax is and what kind of value it can add.

Ajax stands for Asynchronous Javascript and Xml. It’s not a new technology or a new programming language, but a new way of thinking that has changed the way web applications work. A combination of different technologies and techniques work together to create an application with the same feel and functionality of normal desktop applications.

Classic web applications work by waiting for users to input information and click a link or submit button. Then sends the whole page to a server where it can be processed and waits for a reply. During this time the user has to wait for the server’s reply before user interaction can continue.

Ajax applications work by requesting information from the server without sending the whole page, the only thing going to the server is the data request and the only thing coming back is the needed data. This causes less load on the server and a shorter response time.

Though flash can add some impressive designer graphics to a site, it has some major disadvantages like vendor dependence and a rare skill set required to do development. When compared to Flash, developing Ajax is more complex but the skills required are a lot more common and less expensive. Because Ajax is a way of thinking and uses languages that do not require licenses, it doesn’t belong to anyone.

Ajax allows web developers to create dynamic interactive web environments that work with the user. This allows more flexibility when designing user interfaces and eliminates some of the restrictions classical web applications have in terms of performance and user satisfaction.

Although it sounds like Ajax is the answer to the web as we know it, it has some important points to keep in mind from a usability point of view. Users still expect web applications to reload and produce a white screen before interaction can continue. It is customary to indicate that processing is occurring and prevent users getting the perception of a broken system or a failed process. Another problem occurs when users are denied the use of the back button because of page requests done with Ajax. Browsers can keep track of classical page requests in the History but because Ajax uses Javascript for its request it bypasses the browser.

Ajax should be used as a tool to enhance web applications, increase usability and make the user’s experience more enjoyable.

Here are examples of sites that achieved this:

remax.co.za	netvibes.com	todoist.com