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 571519
To read all comments associated with this story, please click here.
This is still HTML/JS/CSS right?
by dindin on Fri 6th Sep 2013 19:35 UTC
Member since:

I don't think this in anyway violates the web standards.

The Chrome specific APIs are there for the things that cannot be done with browser/Internet centric stuff. For example, your application needs a UDP multicast socket - you can with a custom plug-in or other wrapper, but now you can write it in JS and run in inside a browser like any other web page/app.

Mozilla is trying to do the same thing with their WebAPI initiative - for the FirefoxOS. If W3C/IETF will standardize on one (or something), then we can run the same apps in other browsers too.

Edited 2013-09-06 19:37 UTC

Reply Score: 7