Cheerp View website

Web Mobile vs. Native Apps – App Designers Discuss Pros and Cons

Editor's review Page 3 of 4

Published 14 Aug 2014

[cont'd] to Native everyday. Speed, notifications, and access to phone functions are still the major benefits to developing Native, but the line is blurring. We're creating very consistent experiences on mobile Web and Native, allowing users to choose how they prefer to engage with Motoroso. 

Alex Littlewood, Motoroso

Make the decision between Web and Native apps with the following data in mind: Conversion rates from click to download on the app store are VERY low (around 10%). Conversion rates for obtaining valuable permissions in the app (address book and push notification) are also big drops in the funnel. Knowing that an app’s conversion funnel is much longer, with many points of drop-off, is key for any developer facing this decision. That said, I personally believe apps are the future.

Shane Walker, Doublie

We at Tabletize think that full Native is the way to go – better performance, better experience, and full use of the device’s hardware and software-specific features, like for instance, iBeacons, AR and push notifications. Even building a 100-page fashion catalogue is not a trivial task with web technologies on mobile, with memory and performance getting in the way. And even if you can manage to work around these issues, you still get a non-optimal experience.

Franco Puppo, Tabletize

For companies such as ours, the portability of an app far outweighs a mobile website. Applications offer a richer set of user experiences, all designed perfectly for one specific person, the smartphone or tablet...