Live data from Hacker News

A new breed of Chrome Apps

chrome.blogspot.com

21–30 of 169 posts

Re: A new breed of Chrome Apps

#21

The new breed of chrome apps has a lot of flaws after I tried to convert my app over: -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async. -The new window format for apps are a huge UI flaw. You can not open an Chrome app in a tab anymo…

Even the older breed of chrome apps had annoying flaws, IMO, when I was playing around with their APIs to get a feel for them about 6 months ago.

I was mostly surprised how it felt that in many ways you were actually more restricted than you were with just a normal web app. Also the documentation was trash and confusing in a lot of ways because even prior to these changes they had made a lot of other changes via deprecating APIs and their documentation was poorly managed to the point where it was really difficult to determine which APIs were deprecated or not without trying to use them in the latest Chrome and having them fail on you. Also, there wasn't a clear roadmap as to what APIs you could expect to be pretty stable and what ones they might suddenly deprecate, breaking your app.

Hearing that the "new breed" has some of these same flaws and some new ones makes me very disinclined to bother checking in with the current technology.

Re: A new breed of Chrome Apps

#22

The new breed of chrome apps has a lot of flaws after I tried to convert my app over: -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async. -The new window format for apps are a huge UI flaw. You can not open an Chrome app in a tab anymo…

> -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async.

I belive this is only localStorage right? (indexedDB is still available afaik)

Firefox OS had mentions of disabling localStorage, its been a huge problem due to its synchronous API, I dont think it did end up being disabled though, I would really like to see localStorage being (slowly) deprecated and an async api (possibly even just a helper for idb) being promoted as an alternative full web standard as opposed to chrome specific API's coming in here

Re: A new breed of Chrome Apps

#23
This is, effectively, bringing a ChromeOS-like app interface to Windows (and soon other platforms). The new app launcher looks just like it does on ChromeOS, putting Chrome Web Store apps on an equal footing with native apps started from a Start menu or equivalent.

Re: A new breed of Chrome Apps

#24

Prediction: The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?

I don't know if the convergence will happen, but they certainly need to fix WebView in Android to at least allow migration. It's still using the old Android Browser and is severely outdated (no WebSockets, etc). My guess is that Chrome Packaged apps will be the replacement for WebViews on Android. Anyone who wants a stop gap though, should check this out: https://github.com/pwnall/chromeview

A WebView in a native app always seemed like a really hacky way of doing it, so a proper Chrome App functionality would be fantastic. Just like how Firefox does it (even on Android, in the Aurora builds)

Re: A new breed of Chrome Apps

#25

Prediction: The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?

As an Android dev I can tell you this isn't happening in the next 5 years. They may add Chrome apps to Android, but it will be a niche option that won't be used by anybody.

My utopic wish is a new open platform that will combine strengths of the web and of operating systems (Windows, Android):

- Web: Great for documents, which it was originally designed for. Automatic updates. No installation. You can "fork" an app / document by middle clicking a link.

- Operating systems: Great for apps. Speed. More low level access to the hardware. Much richer platform than the web (window mnagment, human interface guidelines, ...).

Re: A new breed of Chrome Apps

#26

Prediction: The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?

As an Android dev I can tell you this isn't happening in the next 5 years. They may add Chrome apps to Android, but it will be a niche option that won't be used by anybody. My utopic wish is a new open platform that will combine strengths of the web and of operating systems (Windows, Android): - Web: Great for documents, which it was originally designed for. Automatic updates. No installation. You can "fork" an app /…

Why, as an Android dev, do you say that?

Re: A new breed of Chrome Apps

#27

The new breed of chrome apps has a lot of flaws after I tried to convert my app over: -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async. -The new window format for apps are a huge UI flaw. You can not open an Chrome app in a tab anymo…

> -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async. I belive this is only localStorage right? (indexedDB is still available afaik) Firefox OS had mentions of disabling localStorage, its been a huge problem due to its synchronous API,…

Synchronous local storage on a phone would be a real problem due to lags, on desktop it might be OK...

Re: A new breed of Chrome Apps

#28
post #9
post #5

Earlier quoted context omitted.

It looks like they open up APIs that otherwise wouldn't be exposed, like access to the shell and devices.

Cool, Java Applets reborn

I don't see much wrong with the concept behind Java applets. Small downloadable apps that run on multiple platforms, backed by a universal runtime.

The execution was awful, but still.

Re: A new breed of Chrome Apps

#29

It would be nice if the apps they recommended (wunderlist) actually worked. I have attempted 5 times to "sign up" for the wunderlist app, every time I hit the button the app freezes on the load screen. Not once has it made it past. I also have not received one email verifying my attempt to sign up. My first experience with app launcher and one of the apps would be horrible. Better get on the ball if you really wanna…

Just and FYI, if anybody is having this same issue, if you go to the website (not using the app on your desktop) you can sign up there, then you will be able to sign in.

Re: A new breed of Chrome Apps

#30

The new breed of chrome apps has a lot of flaws after I tried to convert my app over: -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async. -The new window format for apps are a huge UI flaw. You can not open an Chrome app in a tab anymo…

> -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async. I belive this is only localStorage right? (indexedDB is still available afaik) Firefox OS had mentions of disabling localStorage, its been a huge problem due to its synchronous API,…

indexedDB is available with an entirely async API. Bring on the callbacks!
Post reply on HN