Linked by Thom Holwerda on Fri 6th Sep 2013 15:22 UTC

The new apps look and behave much like the native apps you find on Windows and OS X. They're built using web technologies, but also with Chrome-specific code that means they won't be able to run on other web browsers - they're truly Chrome apps. They can exist outside of your browser window as distinct apps, work offline, and sync across devices and operating systems. They can also access your computer's GPU, storage, camera, ports, and Bluetooth connection. Chrome Apps are, for now, only available through Chrome on Windows or Chrome OS on a Chromebook. Mac users will have to wait another six weeks before their version of Chrome will be updated.

This is very important for Chrome OS - since this means it can now have applications outside of the browser. Google's plans for Chrome OS suddenly became a whole lot clearer.

Permalink for comment 571531
To read all comments associated with this story, please click here.
Member since:

I can actually buy this argument.

When it all comes down to it I think it depends on how much control google tries to maintain over chrome and the chrome api, and how rich/complex that api is internally.

If the chrome api is mostly a thin layer that abstracts away mostly OS calls and doesn't promise to provide the kitchen sink then that would make it less evil than something like flash that no one seems to have been able to properly reimplement (or mono/silverlight for that matter).

I know that at one point fltk was ported over to run on chrome NaCl which implied that NaCl itself was fairly low level (I would assume google chrome apps would be NaCl).

Edited 2013-09-06 21:08 UTC

Reply Parent Score: 3