Platform specific "apps" vs. HTML-based "apps"?
Posted Dec 13, 2012 0:28 UTC (Thu) by dowdle
In reply to: Platform specific "apps" vs. HTML-based "apps"?
Parent article: A simulated FirefoxOS experience
so why would you tolerate awful restrictions of webapps if there are no upside?
Because as I said, a significant number of "apps" are really just front-ends to web-based services that should work fine in a browser. Having to maintain custom builds for each environment is the opposite of what is desired by developers.
And this is different from what happens on desktop, console and other places… exactly how?
Because Apple (and Android to a much lesser degree) is/are constantly referring to the large number of apps they have... and that there is "an app for that". We just don't hear "there's a webapp for that" when it is really also the case.
There is also a mis-perception that making mobile apps is a potential gold mine... but I think the gold rush is mostly over.
Why do you think Android or iOS can not be extended to become usable on desktop, too?
It is probably easier to take a mature desktop OS and scale it down for small screen with touch features... than it is to scale a simple GUI shell up to a full-blown desktop environment. That is obviously just conjector on my part. Of course we know that Android has a (modified) Linux kernel underneath. The main features for developers are the APIs and various libraries for things. I haven't really seen any serious productivity apps for Android (Softmaker Office and the stylus apps from the Samsung Galaxy Note perhaps?) but I'm sure they do exist. From what I understand the vast majority of games for Android are written in C++ and completely avoid the Java bits. So I have no hard evidence other than Colberting.
to post comments)