chrome: becoming more os-like after all…
Saturday, February 26th, 2011 at 11:24 am by Brian Ales
A week or two ago I wrote about Google’s Chrome web browser to complain that the first three Chrome web “apps” I “installed” turned out to be nothing more than simple bookmarks to Flash-enabled sites available on any web browser. What really bothered me, though, was Chrome’s disingenuous user interface. The “app installation” process was in fact nothing more than the simple and instantaneous saving of a URL string as a bookmark – yet in an apparent attempt to convince the user there was more going on than there actually was, Chrome went as far as displaying a spinning progress wheel for a second or two. It’s my suspicion this progress wheel was merely a ‘prop’.
And this illustrates the challenge facing Chrome as it transitions from the ‘browser-as-application’ it is today to the ‘browser-as-operating-system‘ of tomorrow:
While Chrome OS will enjoy certain thin-client advantages (instant-on, greater ease-of-use, and near immunity to malware), these advantages alone aren’t enough to make for a compelling product (or it would have already happened). As the essence of the operating system, the Chrome browser will also have to differentiate itself from all the competing standalone browsers out there running Flash (and in a few years, HTML5). In other words, Chrome must evolve beyond the conventional browser paradigm: there has to to be some degree of Chrome value-add in terms of increased functionality and/or performance.
Well, this week Google made a step in that direction: Chrome web apps can now run in the background as processes, even when all Chrome windows are closed. This will allow for asynchronous user notifications and the preloading of content into local memory – but more importantly, with Chrome OS devices expected to launch later this year, it’s an indication Google is hard at work after all on the kinds of ‘browser 2.0′ innovations required to make Chrome OS a success.


Post your comments »


