The real purpose of Chrome is to run web applications. Google would like it to be Google applications, of course. Here’s a few things I noticed.
2. Chrome includes Gears, which enables offline functionality and other useful services, like a local database engine.
3. This is really part of Gears; but it’s worth noting separately. The Gears Desktop API lets you create application shortcuts – without further permission, apparently. In Chrome this is surfaced as a Create application shortcut dialog:
Note that this is a browser dialog, not a web page dialog.
Why is this a big deal? Well, I recall Adobe’s Kevin Lynch telling me that the usability issue around navigating to an URL in order to run an application was one of the motivations behind the development of AIR, Flash on the desktop. Google reckons it is easier to deal with the usability issue, than to create a separate desktop runtime.
4. Web applications started from shortcuts have no browser furniture. Just the web page in a window. There are probably other ways to get this effect too. I noticed that if you type Ctrl-T while in one of these full-window Chrome pages, which normally starts a new tab, it actually opens a second Chrome window, not just a new tab. Google wants that shortcut to behave like an application, not like a web browser.
3 thoughts on “Google Chrome: the developer angle”
> lets you create application shortcuts – without further permission, apparently
Because the shortcuts are just created in your user profile.
I noticed that Chrome installs itself in C:Users[USERNAME]AppDataLocal – which is unusual. Not sure what impact this has on the permissions it is allowed to created those shortcuts?
I think gchrome is great, amazing how fast the developers have made it. It looks very clean as well, simple, easy to use. A winner for sure. Any ideas on the direction it is headed after the beta?
Comments are closed.