In the keynote presentation of The Ajax Experience in Boston, Alex Russell and Joe Walker posed the question "What's needed to take development in the browser to the next level?"

The current level of Ajax toolkits are a result of IE winning the browser race, and all browsers vendors entering a period of stability. Stagnation in browsers features meant that to provide new application features, libraries needed to be developed. And the libraries today have provided good solutions to the holes in browser functionality, as well as providing a browser compatibility layer for developers.

To progress past the plateau, Alex and Joe provided thoughts in the categories of features, reliability, trust and momentum that need to be addressed.

1. Features

Although new features are needed to advance the user experience, they need to be added with care. It will be important that any new features do not break existing ones, and that features are added ubiquitous by al vendors.

In fact, new features are not being introduced by browsers, instead they are provided by Ajax libraries. Therefore, the important question that needs to be answered is "how far can the libraries go?"

Libraries are pushing the limits with features such as Comet, 3D (VML/SVG/Canvas), and storage and downloads.

Another issue that will continue to plague the use of new browser features is the depreciation of the browser itself. Even if new features are introduced into a new generation of web browsers, the browsers currently in circulation may take 5 or more years to be removed. This will increase the responsibility of the Ajax toolkits, to assist in the transparent transition between generations of browsers.

2. Reliability

Reliability is going to be an important characteristic of new web browsers, as broken content is the rule rather than the exception. This is not a new problem, and web browsers will need to continue with the precedent that they have already set in being able to handle incorrectly formatted content. Similarly, there will continue to be more than one technology. As well as the currently support different versions of HTML, CSS and JavaScript, there will be new versions and new technologies to deal with.

We need to be learning from biology and provide browsers that can cope with failure, and at the same time evolve.

3. Trust

So what can go wrong? There are many concerns that developer have today, these include:

• Web Worms
• Privacy invasion
• Data in transit
• Identity theft
• Browser security
• How to build something trustable

New generations of browsers should be able to assist developers in building secure and trustable applications. In order to do this, reliable patterns need to be developed, and these patterns will need to:

• Responds in the way that you, the user, expect it to respond
• Follows the principle of least astonishment

There are a lot of ways to break user trust - we need to turn this around. The suggestions Joe and Alex made for features to assist developers are:

• Content restrictions (block based)
• An anti CSRF marker for cookies
• Sandboxing
• Less brittle models of building relationships (SMASH/XIP/etc)

4. Momentum

Fortunately the web has already gained huge momentum, being the preferred delivery mechanism of today’s applications. And for the web, developers are providing mass and the number of deployed browsers providing velocity.

As developers, we can participate and influence standards bodies to continue momentum, and continually improve the technologies we are using.

We need to reinvigorate standards bodies, with the resulting process being transparent as well as available and driven by user and the community.

Momentum is also being provided by the browser vendors, who are moving forward without specifications. They are taking risks and we should encourage them. In particular, plug-ins are providing a way to break the non-native world, and a question all web developers should be asking themselves is "will the next version of development be via browsers or something that piggybacks on a browser?"

In conclusion, Alex and Joe asked another question, this time rhetorical:

With Ajax toolkits and plug-ins, have we provided a solution so that web browsers don't need to evolve?