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.

Timestamp 36:20 or so... Im really posting this for the benefit of others, I can tell from your tone you are a lost cause.

Yet, they require you to have a web login to use them, oh the irony.

No they do not. They have unfortunately made it more difficult, but it is not impossible. If you launch chrome with the "--enable-easy-off-store-extension-install" switch, you can install them from anywhere, no login required. And you never needed a login to run them - that is straight up bullshit.

I will agree that I think they should change this policy, or at least come up with a different mechanism to protect users from malicious extentions - but again, they have not removed this ability - they more or less hid it behind a runtime flag.

And how can they try to commit a standar w/o concensus, "Hey this is what I'm doing, I'm ignoring you and making my own standars, you can try to implement them, btw, I used just chrome sprcific API, so goof luck trying to emulate them, wnat more details? get a G+ account."

Im sorry but it is you who have no idea how this works... The way the W3C process works is you initiate a working group in order to achieve consensus - but you do that after you have a working implementation. Its not the f*cking mob - no one has to go ask the godfather if it is ok to do something. Every single standard in the W3C started off this way.

It is really weird, cause I looked for information and all there is is just that fragment of the video, nothing else, do you have any other link?

I have not seen any specific RFCs or anything at this point, things like this move pretty slowly... But they did publicly announce intentions to put this on a standards track - Im NOT spreading lies...

I know how the w3c standard works, some one needs something, it implement it then submitted as a standard, I wouldn't call the best way.

Whats the alternative? Sit around talking about all the cool stuff they could do and waiting until everyone agrees before actually doing anything? Yeah, that would work, if your goal is to never get anything done...