Interface Design For Ajax

Interface Design For Ajax

Looking at Ajax From a Design Perspective

Just as with all new technologies, the usage and adoption of Ajax must become widespread if the program is to be a success. In addition to this, there is almost always the possibility that the technology will be used in a way that its inventors never intended. The World Wide Web is not beyond this phenomenon, and there are a number of Internet technologies that have been handled in a way that its inventors never wanted. Some of these include downloading lots of Java applets for a basic page navigation, the use of flash movie for various types of animations, and frames that block bookmarks and the ability to share URLs.

Many of these technologies have been abused to the extent that they are permanently damaged. Flash has become closely associated with intros that are often skipped by users, and many users are also annoyed by Java applets when they are placed within web applications. In fact, some experts feel that people have been so bombarded by bad experiences regarding client side Java that it has become hazardous to advise anything that is not HTML. Why is this all important? Because Ajax is in its infancy, and it is very susceptible to many of the problems which plagued both Flash and Java applets.

Design Implications of Ajax

It is important for the developers who wish to use Ajax to learn how its inventors intended for it to be used. The last thing we need is a future where people consider Ajax to be an annoyance, and find ways to "skip" it like they do many Flash intros. Ajax was designed to be fast and interactive. The inventors want it to be used in the creation of web applications that are quick and responsive. The technologies which fall under Ajax include DOM, XMLHttpRequest, and asynchronous JavaScript. Interface web designers who are looking to make their applications more dynamic will want to use this tool.

Perhaps one of the most impressive things about Ajax design is that web applications can be updated without having to reload the entire screen or page. When you use Ajax, a single call to a server will be capable of updating one element, and this can be done with the data that is taken from the server. Because the user doesn't have to worry about reloading the entire screen, the application will be more responsive to the actions of the user. However, it should also be noted that updating only specific elements on a page can be done without the use of Ajax.

Why Ajax Must be Used in the Way It was Intended

In the past, many web applications used frames to have individual elements on a page updated. The difference between these older methods and Ajax is that any element defined with DOM can be highly dynamic, and data can be uploaded from the background without any action from the user. This makes it readily available whenever the user needs it. To see this system in action, all you have to do is use Google Maps. It is the very definition of what I'm explaining here. Google Maps will load images which are likely important for behind the scenes.

Ajax is powerful because it allows all the elements on a page to be altered individually and quickly, and it can be done in a way that will not effect the rest of the interface. Most of the people who use the web are not yet used to this. However, when they use it for the first time, users will become aware of the fact that their action creates a reaction, and this reaction will occur immediately. The Ajax updates are so fast that the user may not even notice they happened.

Conclusion

Ajax has a great deal of potential, but so did Flash and the Java applet. The ways in which developers choose to use a technology will determine whether or not its successful. The general rule of thumb is to use the system in the way that the inventor originally intended. While you may like to experiment, using Ajax in an improper manner can lead to an experience that is not beneficial for the user.