This document discusses the debate between developing native mobile apps versus web-based/HTML5 apps. Native apps provide better performance and user experience by leveraging the full capabilities of each device's operating system, but they are more expensive to develop and maintain across platforms. HTML5 apps can be cross-platform more easily but often do not perform as well as native and face challenges rendering rich interfaces. The document also discusses differences in areas like monetization, security, updates/distribution between the two approaches but concludes there is no clear winner and the best option depends on factors like the need for marketplace distribution or prioritizing security.
3. • The great app debate
• May the best app wins, the fight begins
• User Exprience
• Performance
• Monetization
• Security
• Cross-Platform costs
• Updates and Distribution
• And the winner is…
• Quiz time
• Q&A
5. ‘’ A native mobile app is a smartphone application that is
coded in a specific programming language, such as Objective
C for iOS and Java for Android operating systems. Native
mobile apps provide fast performance and a high degree of
reliability. …. ’’
http://www.techopedia.com/definition/27568/native-mobile-app
11. USER EXPERIENCE
Only native apps can deliver
the best user expriences
leveraging the full capabilities
of the device and OS to offer
innovative ways of doing
things.
12. ‘’The biggest mistake we made
as a company was betting too
much on HTML5 as opposed to
native. It just wasn’t ready.‘’
— Mark Zuckerberg, Sep. 2012
14. ‘’Our view is that HTML5 technologies can deliver as-good-
as-native experiences – and that will continue to be the
focus for our core application, where we’ll continue to
improve our performance on all devices. And we were all
extremely impressed by Sencha’s Fastbook which is a
testament to the ability to deliver great experiences using
web technology. But the lesson from Fastbook is that it’s
hard work – you don’t get those experiences out-of-the-
box. And the lesson we’ve learnt over the last 12 months
has been that the cost in time, effort and testing to bring
an HTML5 application to a native level of performance
seems to be far greater than if the application was built
with native technologies from the get-go.’’
15. PERFORMANCE
HTML5 still faces challenges in
accessing device-native
features across all mobile
browsers, and in rendering
graphically-rich user interfaces
and data presentations.
16. MONETIZATION
Google Play Store has 500k
native apps, 15 billion
downloads.
On the other hand, Web apps
have no Play Store-ish
Marketplace except
openappmkt.com
17. SECURITY
A native app’s source and
cache is encrypted.
On the other hand, a web app’s
source is much easier to
access and corrupt.
18. CROSS-PLATFORM
DEPLOYMENT COSTS
Native apps require a new
development and testing
process for each platform.
HTML5 was built to be the
common language of the Web
regardless of the device or the
OS.
19. UPDATES AND
DISTRIBUTION CONTROL
Web is an open platform which
is not under a monopoly of any
companies like Google, Apple
or Microsoft.
However, HTML5 is a bit slow
in supporting new phone
features as device makers
innovate.