• 1
• 2
• 3
• 4
• 5

ajax app application applications ashko asynchronous asynchronously backpackit browser button changing character code content cool cut data design developing development engines feature functionality gmail great html index interesting interface javascript js learning links loading lose lot major means move navigation nov open page people place post problem problems program reading remember replace running scroll scrolling search server side site source standards state technology text time title tool top user users view wait web websites world

Keyword Cloud Navigation Map

Using Ajax for the sake of Ajax.

Sure Ajax is cool, and developers love to play with cool technology, but Ajax is a tool, not a toy. A lot of Ajax isn�t seriously needed to improve usability but rather experiments in what Ajax can do or trying to fit Ajax somewhere where it isn�t needed.

Breaking the back button

The back button is a great feature of the standard web site user interface. Unfortunately, the back button doesn�t mesh very well with Javascript. Keeping back button functionality is one reason not to go with a pure Javascript web app.

Keep in mind however that good web design provides the user with everything they would need to successfully navigate your site, and never relies on web browser controls.

Not giving immediate visual cues for clicking widgets

If something I�m clicking on is triggering Ajax actions, you have to give me a visual cue that something is going on. An example of this is GMail loading button that is in the top right. Whenever I do something in GMail, a little red box in the top right indicates that the page is loading, to make up for the fact that Ajax doesn�t trigger the normal web UI for new page loading.

Read Full Tutorial...