> - Consistent used experience, the same app can be built for every device, not duplicated (at least) 3 times which will lead to inconsistencies. Unfortunately

> - Consistent used experience, the same app can be built for every device, not duplicated (at least) 3 times which will lead to inconsistencies. Unfortunately, this also means that every application will offer an inconsistent UX to their users, as there is no adherence to any platform standard. > - Intercommunication, I can right now, open a web app on my mac, start using it, then send my current screen to my phone The ability to save state on a server is not constrained to applications running in a browser. > - Availability, I have an app on my phone with my data that works offline, I still want to be able to access thing same thing using someone elses computer / phone. You can do this with native applications as well, however, one of the significant market shifts that has occurred is that you don't have to. Logging into websites from public computers was always a significant security risk and a trade-off between user experience and convenience; it was simply an inefficient solution to the problem of not having your own, locally trusted hardware. With the introduction of lightweight, high-performance mobile computing devices using always-on internet access, the need to access your Yahoo mail from a 3rd party's computer has all but disappeared for a large (and growing) percentage of the population.