Since Chrome already has an 'appstore' for web-applications, I think it is safe to assume similar facility will find its way into Android devices.
This will probably bring more native capabilities and will let the user allow/restrict the application in terms of accessing the device HW.
It will also make it easier to monetize such applications -- assuming they somehow prevent users from downloading the apps and bypassing the appstore.
While I would agree that Chrome, in some flavor, should be a part of Android, I wouldn't assume that Chrome is destine to be a part of Android. The Chrome and Android projects seem to be dueling strategies at Google.
Re:Native Android vs Html5
by jasonparallel on Wednesday May 18, 2011 @12:13PM
(#2560618)
Check out http://www.phonegap.com/ for packaging html based apps for the platforms. As a added bonus you get access to native app features through javascript.
I suppose my point was that if HTML5 was important for Android, that Android would include the support for web apps in the platform with no outside dependencies.
Re:Native Android vs Html5
by jasonparallel on Wednesday May 25, 2011 @08:18AM
(#2583690)
http://www.youtube.com/watch?v=4f2Zky_YyyQ Google IO vid on the topic
As far as I know, right now web apps have to be accessed through the browser, which means setting up bookmarks and web apps have very little access to the hardware on the device.
Perhaps what the article should be saying is that we should develop for WebOS because it's all HTML/CSS/JS and therefore much easier to develop for since it's all web-based.