html5 vs. native apps: demystifying the decision making process
DESCRIPTION
HTML5 vs. Native Apps: Demystifying the Decision Making ProcessTRANSCRIPT
Welcome. @propelics @itexico
Questions, Commentsto #mobilestrategy
HTML5 vs. Native Apps: Demystifying the Decision Making Process April 11th, 2013
#mobilestrategy!
Propelics Background – About Us
• 15+ year track record • Fortune 500 clients • Global experience • 100% focused on mobile
for the Enterprise • San Jose, Boston,
Pittsburgh
2
Propelics creates mobile strategies and world class Apps for the Enterprise.
Trusted by companies like yours:
• Enterprise Mobile Strategy Services Enterprise Mobile Strategy Mobile App Portfolio Mobile App Scoping & Planning IT Readiness for Mobility BYOD and MDM Strategy Innovation through visualization Center of Excellence Creation
• Mobile Advisory Services Mobile Mentoring Executive Education Speaking Engagements
• Mobile App Development UX Design Onshore and Offshore App Development Mobile App Architecture Prototype Factory
What We Do
#mobilestrategy!
iTexico Background – About Us
4
Your partner in building and managing mobile and technology solutions
Some of our clients:
Collaboration!
Technical!Expertise!
Fast to Market!
IP!Protection! Value!
What We Do Application Strategy &
Architecture!
UI/UX !Design!
Cross-Platform Mobile
Development!
Website & Backend Development!
Testing & Quality Assurance!
Deployment, Maintenance &
Support!
• HQ in Austin, Texas
• Near shore Software Development Center in Guadalajara, Mexico.
• Western Region Office in Silicon Valley.
• Focus on Extended Team As A Service (eTaaS)TM and Cross Platform Mobile Solutions
#mobilestrategy!
Adam Bookman: Partner - Propelics
Adam has been the brains behind many mobile product and program launches. He has advised companies on mobile strategies for Business as well as IT.
He continues to be a “Trusted Advisor” to some of the leading brands around the world. Adam is frequent speaker at conferences related to mobile.
6
#mobilestrategy!
Richard Dutra: VP Business Development - iTexico
Richard is a Silicon Valley executive and entrepreneur who loves building startups and being part of ground floor companies. He believes mobile will be the single most important device we own and its capabilities are endless.
His mission is to empower organizations by helping them realize their mobile strategies and transforming them into meaningful solutions.
7
#mobilestrategy!
Agenda!
• Market Trends • The HTML5 vs. Native Conundrum
• 6 Considerations in deciding HTML5 vs. Native
• Q&A
Missed your topic? propelics.com/lets-talk!
8
By 2015, 70% of your customer
interactions will originate from a mobile device…”
Source: Gartner 2011
2012 was the year of planning for mobile.
2013 is the year
of action.
Source Yankee Group, 2011 and 2012
Transition from B2C to B2E and B2E2C!
Drivers are beyond “BYOD”!
Beyond Cost Savings!
Organizations are beginning to identify how mobile can impact their core metrics!
The Mobile War is Over. The App Has Won.
Source Flurry Analy=cs, comScore, NetMarketShare
Source ReadWrite Mobile
Regardless of CIO need, it’s the experience that creates the demand.
#mobilestrategy!
#mobilestrategy! 15
HTML5 or Native?
An uninformed decision can result in considerable extra expense, dissatisfied users and poor performance and
experience.!
Demystifying the HTML5 vs. Native
Decision
6 Key Considerations
1. Let the Mobile Use Case Drive the Decision
2. Availability of Development Skills 3. Maintenance and Support 4. Performance 5. Security 6. Avoid Re-Litigating the Decision
for Every App Idea
#1. Let the Mobile Use Case Drive the Decision
Avoid Square Peg – Round Hole Syndrome
#1. Let the Mobile Use Case Drive the Decision – HTML5
The site http://mobilehtml5.org/ is a good resource that maps specific HTML5 functions vs. different mobile browser versions !
21
Pros!Cross Platform Deployment Cost!Update Speed !Availability of Skill Sets!Support Multiple Platforms!Quicker Learning Curve!No App Store Approvals Needed!
Cons!Performance!Pixel Perfect UX!APIs to Platform Specific Features!Extensive Offline Support!App Monetization!Inconsistent Browser Support!
22
Intermittent Experiences Large Diversity of Devices / OS (Public Facing or BYOD) Content Centric Consumption Traffic from Search / Social Security of Data at Rest Primarily Connected Access
#1. Let the Mobile Use Case Drive the Decision – HTML5
#1. Let the Mobile Use Case Drive the Decision – Hybrid
23
Pros!Mix Web Code with Native Wrapper!Less Code to Support Multi-Platform!App Store Experience !APIs to Access Device Features!Make Changes w/o Resubmit to App Store!
Cons!Performance – Browser Dependent!Requires More Specialized Dev Skills!Native Apps that Don’t Look Native!Risk of App Store Rejection!Extensive Offline Support!Inconsistent Browser Support!
Gartner predicts that by 2016, over 50% of Mobile apps deployed by the enterprise will be Hybrid.!
-Gartner Predicts Feb. 2013!
24
Accommodate Multiple Platforms Deliver “App Store” Experience Content Centric Consumption Direct Traffic Ability to Utilize More Native Controls Better Offline Support
#1. Let the Mobile Use Case Drive the Decision – Hybrid
#1. Let the Mobile Use Case Drive the Decision – Native
25
Pros!Rich User Interface!Best App Performance!Most Secure!Hooks into all the device APIs!Extensive Offline Support!Monetization!
Cons!More Difficult to Support / Maintain!Increased Time to Update / Distribute!Skills Can be Hard to Find!Limited App Portability!Expensive!
“The CIO may think they are going to spend the next two years deciding what the next hybrid app framework is. In the meantime there will have been an awful lot of iOS and Android apps built.”!!
- James Governor – RedMonk!
26
Heavily Used Needs to be Fast Use of Device Features like Camera, Calendar, Notifications, Orientation, Shake, NFC User Experience is Paramount Interaction Drives Business Process (Decision Making in UI) Security and Distribution Control are Important Offline / Store and Forward Use Case
#1. Let the Mobile Use Case Drive the Decision – Native
Resist the One-Size Fits All Temptation
#2. Availability of Development Skills
#2. Availability of Development Skills
29
• How many platforms & form factors will you decide to support? If you are planning to build a Native App, pretty much each platform is going to need at least one developer.
• Chances of finding someone who is good at all three development platforms is extremely rare.
• Today, developers familiar with web technologies are more abundant, easier and cheaper to hire than experienced Native developers.
• Experienced front end mobile web developers possess high in-demand skills.
• If you are going the Hybrid route, again, you are looking for someone with the above JavaScript knowledge and knowledge of the platforms you are using.
#3. Maintenance and Support
#mobilestrategy!
#3. Maintenance and Support
31
Two factors complicate the situation for Native/Hybrid Apps over Web Apps.!!
• You need the user to download the latest version!
• In the iOS App store there is a lag of up to a week. In Web Apps, you don’t face these challenges; your users are always using the latest version!
• Develop an ongoing App Support Plan to protect your investment!
#4. Performance
#mobilestrategy!
#4. Performance
33
A central part of user experience is performance of the application on the mobile device. !
• Performance comes in two forms: rendering and loading.!
• Disparity in performance between Native Apps and HTML5.!
• The performance gap between HTML5 and native is so great that even non-technical users easily notice the difference.!
#5. Security
#mobilestrategy!
#5. Security
35
Along with Performance, Security is one the bigger advantages Native Apps have over Web based Apps.!!• Source Code Visible!• URL based Vulnerabilities!• Data on Device!• Data in Transit!
#6. Avoid Re-Litigating the Decision for Every
App Idea
#mobilestrategy!
#6. Avoid Re-Litigating the Decision for Every App Idea
37
Build a Framework for HTML5 vs. Hybrid vs. Native Decisioning: • Consider User Population, Supported Devices
• Customer or Employee?, Corporate Owned or BYOD, Tablet or Phone • US Statistics:
• Corporate Activations: iOS 77% of activations (and rising), iOS and Android account for 99.7% of all corporate activations smartphones and tablets
• BYOD: At least for now, native = iOS and Android • Public Market: iOS and Android account for 91% of smartphone activations
• Process Innovation vs. System Access • Control Over Device Types?
• Approved BYOD (reduces Android diversity) • App Use Case
• Location, Connectivity, Frequency of Use, Business Criticality, Brand / Visibility, App Functionality
• Performance • Security • Maintenance / Support
1. Let the Mobile Use Case Drive the Decision
2. Availability of Development Skills 3. Maintenance and Support 4. Performance 5. Security 6. Avoid Re-Litigating the Decision
for Every App Idea
One More Consideration:
The cost of doing nothing due to “Analysis Paralysis”
#mobilestrategy!
Propelics Kickstarts
Propelics & iTexico Special Offer
Free 1 Hour Mobile Advisory Call
[email protected] 888-405-2820
40
Mobile App Scoping & Planning Kickstart
Mobile App Roadmap
Mobile Center of
Excellence
Mobile App Rapid
Prototyping
IT Readiness for Mobile Kickstart
Prototype Factory
#mobilestrategy!
Thank you (Q&A)
@propelics @itexico
• Innovation Focus
• Engaging Process
• Mobility Centric
• Experience Across Industries
• Enterprise Solutions
• Advisors, Strategists, Implementers
• Strategy at the Pace of Mobility