There is no which is better between Mobile Web and App - it all depends on the product and service. The next link might clarify better this debate for you.
Why the mobile web vs. apps debate is a false dichotomy
The arguments presented in favor of the mobile web over mobile native represent a false dichotomy. Simply put, there is no universal truth in the mobile web vs. mobile native debate, and no “one right way,” despite what the pontificators would have you believe.
The argument in favor of mobile web goes like this:
The web is open, ubiquitous, requires no special software, is globally searchable and algorithmically discoverable. As such, it is agile, extensible and readily manageable. Plus, there are lots of proven models for development, discovery, distribution and monetization. And, of course, mobile web development offers a higher degree of symmetry to PC browser-based web development than mobile native app development does.
The argument is favor of mobile native goes like this:
There are over 400 million iOS devices and over 500 million Android devices, representing almost 1 billion devices worldwide. In the case of iOS, Apple has built a well-managed development, distribution and monetization platform that has yielded tremendous innovation and user engagement in areas ranging from photography to gaming, social networking, entertainment, education, music and other rich media.
On some level, the argument comes down to “good enough” and “universal” vs. the “richest possible experience” on the device type that is subsuming the PC.
Mobile web devotees make three arguments against the long-term viability of mobile native apps. One, they argue that it’s just a matter of time before HTML 5 gets “good enough” to obviate the need for distinct mobile native platforms.
Two, they assert that because mobile native apps are tied to app stores, this overly restricts what developers can do, thereby throttling innovation.
Three, they argue that app store economics don’t make sense. Native apps cost more to develop than web apps. Discovery within the app store is hard and giving up a 30% cut to Apple (in the case of iOS) is expensive.
To be clear, the browser is functional and essential, but it’s a crap piece of software. In other words, it could easily be another decade, and we’ll still be having this same conversation.
Two, if the app store model is throttling innovation, then I want more throttling because what I see in terms of the range of app types, and their design and implementation is a rain forest of diversity. Meanwhile, I am still waiting for even one mobile web app that stops me in my tracks.
Three, however, is where the real meat lies. Mobile native apps are more expensive to develop, and while Apple can proudly report that it’s paying billions of dollars to iOS developers, the messier truth is that approximately half of those dollars are going to just 25 developers.
That type of split between the mass of makers and the relative few takers is not sustainable in terms of cultivating a thriving, sustainable independent developer class, something that I blogged about previously (see ‘The iPhone, Angry Birds and the Pink Elephant‘).
Nonetheless, it’s a false dichotomy to suggest that native app economics is an argument against mobile native, and in favor of mobile web.
The arguments presented in favor of the mobile web over mobile native represent a false dichotomy. Simply put, there is no universal truth in the mobile web vs. mobile native debate, and no “one right way,” despite what the pontificators would have you believe.
The argument in favor of mobile web goes like this:
The web is open, ubiquitous, requires no special software, is globally searchable and algorithmically discoverable. As such, it is agile, extensible and readily manageable. Plus, there are lots of proven models for development, discovery, distribution and monetization. And, of course, mobile web development offers a higher degree of symmetry to PC browser-based web development than mobile native app development does.
The argument is favor of mobile native goes like this:
There are over 400 million iOS devices and over 500 million Android devices, representing almost 1 billion devices worldwide. In the case of iOS, Apple has built a well-managed development, distribution and monetization platform that has yielded tremendous innovation and user engagement in areas ranging from photography to gaming, social networking, entertainment, education, music and other rich media.
On some level, the argument comes down to “good enough” and “universal” vs. the “richest possible experience” on the device type that is subsuming the PC.
Mobile web devotees make three arguments against the long-term viability of mobile native apps. One, they argue that it’s just a matter of time before HTML 5 gets “good enough” to obviate the need for distinct mobile native platforms.
Two, they assert that because mobile native apps are tied to app stores, this overly restricts what developers can do, thereby throttling innovation.
Three, they argue that app store economics don’t make sense. Native apps cost more to develop than web apps. Discovery within the app store is hard and giving up a 30% cut to Apple (in the case of iOS) is expensive.
To be clear, the browser is functional and essential, but it’s a crap piece of software. In other words, it could easily be another decade, and we’ll still be having this same conversation.
Two, if the app store model is throttling innovation, then I want more throttling because what I see in terms of the range of app types, and their design and implementation is a rain forest of diversity. Meanwhile, I am still waiting for even one mobile web app that stops me in my tracks.
Three, however, is where the real meat lies. Mobile native apps are more expensive to develop, and while Apple can proudly report that it’s paying billions of dollars to iOS developers, the messier truth is that approximately half of those dollars are going to just 25 developers.
That type of split between the mass of makers and the relative few takers is not sustainable in terms of cultivating a thriving, sustainable independent developer class, something that I blogged about previously (see ‘The iPhone, Angry Birds and the Pink Elephant‘).
Nonetheless, it’s a false dichotomy to suggest that native app economics is an argument against mobile native, and in favor of mobile web.
Comments
Post a Comment