3 ms·
While performance is often cited as the main reason for having a native app, I think that one of the biggest reasons to prefer native apps is usability. More co
by Ingon 13y ago
While performance is often cited as the main reason for having a native app, I think that one of the biggest reasons to prefer native apps is usability. More concretely I can see the following:
- A web app/site is often an app within an app. This means that what usually works as an interface to this device is no longer true, or rather different. The gestures are different, how the app is treating them is different and so on.
- On the performance side the web apps suffer from UI delivery problem - the site must deliver both the app it self and the data for which you use this app. A native app have to work with the data only, and its not restricted to be always connected with the web.
- Another reason is that although the same on the surface mobile is actually shifting our usage patterns. Our usage is far less consistent, more spaced out, under more conditions and with smaller screens. The native apps work well here because their components are thought out to work under these conditions and of course tested for this.
- Finally because of the usage patterns we see some native apps more versed to cover specific use cases. This differs from the mobile web which just have everything the normal web has, but tested to work on mobile.
Some of this points of course can be tackled by html5 wrapped web apps. But this approach comes with own set of limitations and problems - we are compromising on both openness and performance sides. So while I want the mobile web to work, for now I think that native apps are winning.
- Mikeb85 13y agoYour browser can cache a web app to be used offline. Plenty of Chrome apps are packaged this way. Firefox also has an option to do this, and Firefox OS can work without an internet connection. An HTML5 app is just source code obtained from a website that's run through a VM, and may or may not connect to a back-end (usually does though). The problem isn't the web, it's how many web developers choose to use it. If you want to really know how powerful the web is, check out many of the WebGL demos and game demos out there...