
Last week we wrote about dropbox, and how business concerns can sometimes muddy the waters of what (in a perfect world) should be a transparent and open relationship – the relationship between technology and us humans.
The week before, we wrote about Chrome OS, Google’s view of a cloud-based, thin-client future of personal computing.
Here then, is a post combining these two themes.
The other day, I started playing around with the Chrome Web Store. We’ve been interested in the Chrome OS since it was a just a twinkle in Google’s eye, and now that devices running the new ‘browser-as-operating system’ are just a few months away from hitting the market, it seemed like high time to check out these Chrome “apps”.
So I “downloaded”‘ and “installed” a few of these “apps” onto the Chrome browser: a few from Aviary having to do with photo and audio editing, and a music streaming service from from a company called Grooveshark. Initially, I was pretty impressed – I got it. Then I started seeing Adobe Flash prompts popping up when I tried to use the <back> key, and a thought occurred to me – was I looking at a brave new world of Chrome web apps, or was I looking at merely a few simple bookmarks to Flash-enabled websites masquerading as Chrome-specific “apps”? The obvious thing to do was to try accessing these same URLs directly from a different browser, so that’s what I did – and lo and behold, my shiny new Chrome “apps” functioned identically on Firefox - without having anything to do with Chrome. At all.
So mere months before Chrome OS devices are slated to start hitting the market, all three Chrome ‘apps’ I tried out were really just bookmarks to Flash-enabled websites available on any browser. If you’re Google, that’s a problem. What bothered me more, though, was how Google chose to handle that problem: by misrepresenting a simple bookmark as an “App” that “requires Chrome” that’s saved via a button labeled “Install” – all of which is followed by a few seconds of a (completely bogus?) OS X-style spinning progress ring!
In short, the simple saving of a generic bookmark is being made to look like a Chrome-specific “application installation”.
I do want to like the Chrome OS, I really do – but that kind of thing, well, it ticks us off a bit (we hate it when our software is being – let’s say – disingenuous with us).
P.S. Maybe the more interesting aspect of this whole story, though, is how Google will differentiate the Chrome Flash (and later, HTML5) user experience from the Flash/HTML5 user experience offered via competing browsers – because if the Chrome OS is going to gain real traction, there’s going to have to be some additional ‘value add’ to the Chrome browser proposition. In other words, Chrome will have to become extensible in such a way as to allow for optimized (Javascript/HTML5) performance and for more native-feeling (and standardized) user interfaces and control sets than those offered by other standalone browsers.