The release of the new Google Chrome browser may provide a big boost in usability for those embracing advanced Web application design. Our early take on the browser highlights a few key things to consider:
Designed for web applications, not web pages
This has been a thorny issue for several of our clients deploying high volume transactional applications on the web. Things are great at 8am but as the day progresses the browser cannot seem to manage the DOM model and the browser gets unstable after several hours. Try it yourself with a large Gmail account and you’ll see how things get dicey as your day progresses.
Each tab is a separate process
This will go a long way to create a more stable enterprise platform for web applications. Just the fact that one URL can no longer crash all other open pages (tabs) will be a huge win in the enterprise.
Using Google Gears leverages the desktop
Now you get a great infrastructure (Google Gears) to manage client-side persistent data without having to create your own framework. This is bundled with robust garbage collection / memory management to deliver speedy desktop performance.
Go ahead…try it out and let us know how it performs with your robust Web 2.0 applications!