2
edits
Talk:B2G: Difference between revisions
no edit summary
No edit summary |
|||
| Line 40: | Line 40: | ||
Good luck! -- [[User:Skierpage|Skierpage]] 16:55, 26 July 2011 (PDT) | Good luck! -- [[User:Skierpage|Skierpage]] 16:55, 26 July 2011 (PDT) | ||
== Mobile Web OS pros are not clear == | |||
Hi, | |||
I am interested in the idea of mobile web OS, but after contemplating it a bit I have reached a dead end. | |||
First of all, it is not something completely new. A lot of apps on Android platform are just web page wrappers and with mobile frameworks they are getting just better, because it enables communication between hardware and html/js. Phonegap does basically all you want to achieve. Most native apps are also just web service consumers and could have been implemented as web apps if developers would be aware of new technologies. Barely any data is stored only on the phone, so Android could be called cloud OS. | |||
Secondly, have you noticed how terribly slow web apps are on mobile devices. Those developed with frameworks and stored internally are okay, but for example dynamically loaded (even with home Wi-Fi) Gmail is a nightmare. The only solution I see is to cache/save all web apps to phone’s storage, but then how that’s different from current situation on Android. | |||
Chrome OS for laptops are good idea, because it takes a while to set up a desktop environment. With mobile phones it is a different story. You can easily log on to a new Android phone and all programs will be downloaded and installed for you in few minutes. After that you are ready to browse your old files on dropbox or create documents on GDocs. | |||