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

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.

Thread beginning with comment 571560
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: 50 comments so far
by Hiev on Sat 7th Sep 2013 14:54 UTC in reply to "50 comments so far"
Hiev
Member since:
2005-09-27

Google has already submitted this entire framework to the W3C for standards tracking

Is not the same, chrome apps are a totally different story not even compatible with the standar, they use chrome specific functions like this one:

chrome.app.runtime.onLaunched.addListener(function() {
// Tell your app what to launch and how.
})


Even the manifest is different, you are ignorant or misinformed.

- You only need an account to get apps in the web app store, because..

To track you of course.

the web is not HTML and the web is not JavaScript..

And the web is not just Google.

Ummm no. That simple - its not even close.

Care even to elaborate, they are pretty close to me, the sandboxing would be the only difference.

I simply don't get all the Debbie Downer posts about this

Google apologizers never get it.

Edited 2013-09-07 14:55 UTC

Reply Parent Score: -1

RE[2]: 50 comments so far
by galvanash on Sat 7th Sep 2013 23:40 in reply to "RE: 50 comments so far"
galvanash Member since:
2006-01-25

Is not the same, chrome apps are a totally different story not even compatible with the standard, they use chrome specific functions like this one:

chrome.app.runtime.onLaunched.addListener(function() {
// Tell your app what to launch and how.
})


Even the manifest is different, you are ignorant or misinformed.


Did you even read what I said? I said there was overlap with some standards (i.e. widget api and packaging) - not that this was compliant with those standards. It obviously isn't since about 90% of it is completely new functionality that doesn't exist in any standard.

What I specifically said was that they submitted this for standards tracking - Google announced that at I/O when they demonstrated it.

And the web is not just Google.


... and chrome apps are not the web...

Reply Parent Score: 3

RE[3]: 50 comments so far
by Hiev on Sun 8th Sep 2013 01:30 in reply to "RE[2]: 50 comments so far"
Hiev Member since:
2005-09-27

It obviously isn't since about 90% of it is completely new functionality that doesn't exist in any standard.

Then they haven't commited any standar, stop spreading lies.

... and chrome apps are not the web...

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

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."

Edited 2013-09-08 01:48 UTC

Reply Parent Score: 1