Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage News Choosing an Ajax Framework

Choosing an Ajax Framework


Sebastian Just has written about how to select an Ajax framework. He lists a number of questions that architects should answer in helping them narrow down the list of available frameworks, including community and corporate support, learning curve, and whether it fits the type of user the site has.

The questions he suggests include:

Structural Javascript enhancements? Javascript can become a maze if your team does not share a common development methodology . There are so many ways of doing the same thing ( like creating objects of accessing the DOM ) in JS, that you must formalize the way to do it. Such a framework may help via on-demand Javascript, packaging abilities, enhanced OOP...

Re-usability of your written components? Making use of it shall help you in re-using written components in your next projects.

Framework current documentation level? Often low for most projects, you must take care of it

Features you need? You may look at your projects needs ( or near future needs ) and see if the Framework can handle them. Some are GUI oriented, special-effects oriented, Javascript centrics, communication only oriented. None will completely cover your requirements. What is the complexity degree in making the framework evolve ? can you add your own features in the framework ? will you help committers ? Can you mashup multiple Frameworks ?

How long will it last? Most projects are companies own project spin-off. The Framework evolution depends on their ability to maintain and make the project evolve. A good user community is important as well as talking to developers when needed further functionalities. Taking care of sponsors and the framework current uses in production web sites, is a good start in guessing if the Framework will last years or will be stopped in six months.

In a discusion on Ajaxian some other issues are raised including testability and code quality.

An alternative approach to comparing frameworks was covered in December.
We need your feedback

How might we improve InfoQ for you

Thank you for being an InfoQ reader.

Each year, we seek feedback from our readers to help us improve InfoQ. Would you mind spending 2 minutes to share your feedback in our short survey? Your feedback will directly help us continually evolve how we support you.

Take the Survey

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Keeping accessibility and other non-Javascript users in mind

    by Pete Johnson,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Another important aspect when choosing an AJAX framework is to consider those who will never use it. If you choose something like GWT for your visual effects that takes over your entire page rendering you run the risk of alienating someone using accessibility tools, a handheld device, or somebody who has turned off Javascript for reasons that are their own.

    I was pointed to this recently and it really strikes a cord with me:

    That's why I prefer some of the more piecemeal tools that give you a shot at the approach where you provide an enhanced experience for the Javascript user but still a functional one for the Javascript-disabled crowd. Something to consider.


  • Re: Keeping accessibility and other non-Javascript users in mind

    by Michael Neale,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I think its the accessibility tools that have to keep up - at least when we are talking about web *applications* (not just web pages that happen to be mostly dynamically generated).
    Think back to pre web, the same issues happened with any thick client tool.

    Of course accessibility is critical, but using a very narrow and specific presentation technology to "dumb down" so they can work seems counter intuitive. Those tools used to cope with all sorts of wacky windows apps 10 years ago ! - why can't they now? All the info in a dynamic web app is available in the DOM. What about other tech like Flash/WPF and such, they either don't work with those tools, or they have to provide hooks that those tools can use. I think the age of the accessibility tools getting a free ride from text based "simple" user interfaces is rapidly coming to an end.

    The "graceful degradation" is kind of a seperate issue, and has its own benefits, depending on your audience (obviously not everyone needs graceful degradation - google clearly do for their search page, but if you are building a controller for a partical accellerator - perhaps not ;).

  • Visual designer for a GUI framework is esential...

    by Guy Peled,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Check this concept of creating AJAX application that gives you all the tools that you would expect of a GUI framework (Especially for RIA purposes).

  • Re: Visual designer for a GUI framework is esential...

    by Michael Neale,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    yeah looks nice. is quite advanced (for GWT).

    Nice to have GUI designers like we had 10 years ago ! Hooray for progress !

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.