Re:Using Chrome Web Store for App Distribution (by the numbers)
by jent on Wednesday June 22, 2011 @11:40AM
(#2683607)
In my mind, there isn't much difference technically the big question is whether users want a different experience. A certain percentage want a more fluid user flow similar to a native / desktop app. This web app seems to accomplish that using Google web toolkit and decent page load times.
Re:Using Chrome Web Store for App Distribution (by the numbers)
by jackpine on Wednesday June 22, 2011 @12:08PM
(#2683768)
The fact that "linked" apps have access to unlimited caching is a huge win for user experience.
Re:Using Chrome Web Store for App Distribution (by the numbers)
by stanleydrew on Wednesday June 22, 2011 @11:32AM
(#2683556)
Right, but since Chrome's app environment is really just the browser's javascript and rendering environment (perhaps with access to a few special javascript apis) there isn't really anything special about #2 either. In fact, apps that fit into your #1 and #2 bins are the same thing modulo caching.
1) A link to a website, with the link hidden. Going to the actual website provides the exact same experience.
2) A packaged app that is downloaded and contained within the browser. (It may or may not use a web API for some functionality.)
#1 is basically just a bookmark. There's nothing special about it.