HTML5 vs. Native Apps: Demystifying the Decision Making Process
HTML5 vs Native Mobile App Development: Which option is best?
-
Upload
appcelerator-inc -
Category
Technology
-
view
82.075 -
download
7
description
Transcript of HTML5 vs Native Mobile App Development: Which option is best?
vs
MOBILE DEVELOPMENT
MAY THE BEST APP WIN
Any company creating mobile apps today faces an important decision
Each has its advantages, but choosing the wrong one could be costly
A device-specific program tailored to a mobile device and its associated operating
system, such as iOS or Android.
A web-based program designed to run on any mobile device via a browser.
NATIVE APP HTML5 APP
NATIVE or HTML5?
650k iOS
500k Android
94% native
*according to Appcelerator/IDC’s Q2 2012 survey
100k Microsoft
1.25 MILLION APPS TODAY
Only 6% of apps (75,000 out of 1.25 million) targeted for
development in HTML5*
TIMELINESS OF NEWOS INNOVATIONS
UPDATES AND DISTRIBUTION CONTROL
AVAILABILITY OFPROGRAMMING EXPERTISE
USER EXPERIENCE
CROSS-PLATFORMDEPLOYMENT COSTS
FRAGMENTATION SECURITYPERFORMANCE MONETIZATION
HTML5
advocates believe
the user experience
today is “good
enough.”
ONLY NATIVE APPS CAN DELIVER THE BEST USER EXPERIENCES,
LEVERAGING THE FULL CAPABILITIES OF THE DEVICE AND OS
TO OFFER INNOVATIVE WAYS OF DOING THINGS.
DO YOU WANT
“GOOD ENOUGH”
OR DO YOU WANT
THE BEST?
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
paid out to developers
accounts tied to credit cards
HTML5 LACKS AN APP STORE-TYPE MONETIZATION
MODEL. NO MARKETPLACE = FEWER DEVELOPERS.
DIFFERENT TYPES OF BROWSER INTERPRETATIONS
OF HTML5 MAKE “write once, run anywhere” MORE LIKE “write once, optimize everywhere.”
Native apps require a new build-out for every platform.
HTML5 offers the promise of “write once, run anywhere”— but that promise is not a reality today.
HTML5 gives developers complete control of distribution and lets them deliver apps directly to users via browsers, rather
than putting them behind a third-party wall like an app store.
MEANWHILE, HTML5 HAS TAKEN FIVEYEARS TO BE RATIFIED BY THE W3C.
IOS GETS AN ANNUAL NEW RELEASEAND ANDROID FEATURES MULTIPLE
NEW RELEASES EVERY YEAR.
THIRD-PARTY CONTROL, HOWEVER, LEADS TO FASTER INNOVATION
DATA IN TRANSIT (DOWNLOADING AND UPLOADING)
CAN BE SECURED IN BOTH NATIVE AND HTML5 APPS,
BUT SECURING HTML5 DATA COMPROMISES SPEED.
HTML5 SOURCE CODE IS MUCH EASIER TO ACCESS AND CORRUPT.
DATA AT REST (CACHED) CAN BE SECURED AND
ENCRYPTED IN NATIVE APPS - BUT NOT HTML5 APPS.
WHEN YOUR USERS DON’T WANT
TO DOWNLOAD AN APP
WHEN YOUR INFORMATION IS
CONSTANTLY UPDATING
WHEN YOU DON’T WANT APPLE OR GOOGLE
STANDING IN YOUR WAY
WHEN YOU WANT THE BEST
USER EXPERIENCE
WHEN YOU WANT TO MONETIZE
YOUR APP
WHEN YOU WANT YOUR DATA
TO BE SECURE
TO LEARN MORE ABOUT APPCELERATOR’S MOBILE DEVELOPMENT PLATFORM TO BUILD AND MANAGE CLOUD-CONNECTED NATIVE
APPS ACROSS MULTIPLE DEVICES, VISIT
http://bit.ly/VChQ8vhttp://bit.ly/VChQ8vhttp://bit.ly/VChQ8v