HTML5 vs. Native Apps: Demystifying the Decision Making Process


Published on

Does your company struggle with the HTML5 vs. Hybrid App vs. Native decision?

What does this decision really mean?

Do you have repeatable standards in place for making this decision across your app portfolio?

Who should watch this webinar? Business and IT Professionals responsible for delivering enterprise mobile applications to their workforce.

Join Adam Bookman, Co-Founder of Propelics, and special guest Richard Dutra, Vice President of iTexico to hear more about the strategy and tactics associated with the HTML5 vs Native decision.

Watch this information packed webinar to learn:

How the apps vs. web decision fits into your mobile strategy
The pros and cons of HTML5, Hybrid, Native approaches
How to make the right decision
Post-development implications regarding deployment, app management and security

Published in: Technology
1 Comment
  • Mobile apps offer an abundance of benefits to consumers and internal
    employees/operations. The ability to collect and immediately transmit data
    eliminates paper processing, improves data flow, and adds a competitive edge
    to any organization.
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

HTML5 vs. Native Apps: Demystifying the Decision Making Process

  1. 1. Welcome.HTML5 vs. NativeApps: Demystifying @propelics the Decision Making Process @itexico April 11th, 2013 Questions, Comments
 to #mobilestrategy
  2. 2. Propelics Background – About Us •  15+ year track record •  Fortune 500 clients •  Global experience •  100% focused on mobile for the Enterprise •  San Jose, Boston, Pittsburgh Propelics creates mobile strategies and world class 
 Apps for the Enterprise.
 Trusted by companies like yours: #mobilestrategy! 2  
  3. 3. What We Do•  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
  4. 4. iTexico Background – About Us IP! Collaboration! Protection! Value! Technical! Fast to Expertise! Market! Your partner in building and managing mobile and technology solutions
 Some of our clients: #mobilestrategy! 4  
  5. 5. What We Do Application Strategy & •  HQ in Austin, Architecture! Texas •  Near shore Software Deployment, UI/UX ! DevelopmentMaintenance & Design! Center in Support! Guadalajara, Mexico. •  Western Region Office in SiliconTesting & Quality Cross-Platform Valley. Mobile Assurance! Development! •  Focus on Extended Team As A Service (eTaaS)TM and Cross Platform Website & Backend Mobile Solutions Development!
  6. 6. 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. #mobilestrategy! 6  
  7. 7. 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. #mobilestrategy! 7  
  8. 8. Agenda!•  Market Trends•  The HTML5 vs. Native Conundrum •  6 Considerations in deciding HTML5 vs. Native•  Q&A Missed your topic?! #mobilestrategy! 8  
  9. 9. By 2015, 70% of your customerinteractions will originate from a mobile device…” 
 Source:  Gartner  2011  
  10. 10. 2012 was the year ofplanning for mobile. 
 2013 is the year 
 of action.
  11. 11. Transition from B2C toB2E and B2E2C!Drivers are beyond“BYOD”!Beyond Cost Savings!Organizations arebeginning to identify howmobile can impact theircore metrics! 
 Source  Yankee  Group,  2011  and  2012  
  12. 12. The Mobile War is Over. 
 The App Has Won. 
 Source  Flurry  Analy=cs,  comScore,  NetMarketShare  
  13. 13. 
Source  ReadWrite  Mobile  
  14. 14. Regardless of CIO need, it’s theexperience that creates the demand. #mobilestrategy!
  15. 15. HTML5 or Native?
An uninformed decision canresult in considerable extraexpense, dissatisfied users and poor performance and experience.! #mobilestrategy! 15  
  16. 16. Demystifying theHTML5 vs. Native Decision
  17. 17. 6 Key Considerations
  18. 18. 1.  Let the Mobile Use Case Drive the Decision2.  Availability of Development Skills3.  Maintenance and Support4.  Performance5.  Security 6.  Avoid Re-Litigating the Decision for Every App Idea
  19. 19. #1. Let the Mobile UseCase Drive the Decision
  20. 20. Avoid Square Peg – Round Hole Syndrome
  21. 21. #1. Let the Mobile Use Case Drive the Decision – HTML5Pros!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! The site Offline Support! is a good resource that mapsApp Monetization! specific HTML5 functions vs.Inconsistent Browser Support! different mobile browser versions ! 21
  22. 22. #1. Let the Mobile Use Case Drive the Decision – HTML5Intermittent ExperiencesLarge Diversity of Devices / OS(Public Facing or BYOD)Content Centric ConsumptionTraffic from Search / SocialSecurity of Data at RestPrimarily Connected Access 22  
  23. 23. #1. Let the Mobile Use Case Drive the Decision – HybridPros!Mix Web Code with Native Wrapper!Less Code to Support Multi-Platform! Gartner predicts thatApp Store Experience ! by 2016, over 50% ofAPIs to Access Device Features! Mobile appsMake Changes w/o Resubmit to App Store! deployed by the enterprise will beCons! Hybrid.!Performance – Browser Dependent! 
Requires More Specialized Dev Skills! -Gartner Predicts Feb. 2013!Native Apps that Don’t Look Native!Risk of App Store Rejection!Extensive Offline Support!Inconsistent Browser Support! 23
  24. 24. #1. Let the Mobile Use Case Drive the Decision – HybridAccommodate Multiple PlatformsDeliver “App Store” ExperienceContent Centric ConsumptionDirect TrafficAbility to Utilize More Native ControlsBetter Offline Support 24  
  25. 25. #1. Let the Mobile Use Case Drive the Decision – NativePros!Rich User Interface!Best App Performance! “The CIO may think theyMost Secure! are going to spend theHooks into all the device APIs! next two years decidingExtensive Offline Support! what the next hybrid appMonetization! framework is. In theCons! meantime there will haveMore Difficult to Support / Maintain! been an awful lot of iOSIncreased Time to Update / Distribute! and Android apps built.”!Skills Can be Hard to Find!Limited App Portability! ! - James Governor – RedMonk!Expensive! 25
  26. 26. #1. Let the Mobile Use Case Drive the Decision – NativeHeavily UsedNeeds to be FastUse of Device Features like Camera, Calendar, Notifications,Orientation, Shake, NFCUser Experience is ParamountInteraction Drives Business Process (Decision Making 
in UI)Security and Distribution Control are ImportantOffline / Store and Forward Use Case 26  
  27. 27. Resist the One- Size Fits All Temptation
  28. 28. #2. Availability ofDevelopment Skills
  29. 29. #2. Availability of Development Skills•  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. 29
  30. 30. #3. Maintenance and Support
  31. 31. #3. Maintenance and SupportTwo factors complicate the situation forNative/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! #mobilestrategy! 31  
  32. 32. #4. Performance
  33. 33. #4. PerformanceA central part of user experience isperformance of the application on the mobiledevice. !•  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.! #mobilestrategy! 33  
  34. 34. #5. Security
  35. 35. #5. Security 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! #mobilestrategy! 35  
  36. 36. #6. Avoid Re-Litigatingthe Decision for Every App Idea
  37. 37. #6. Avoid Re-Litigating the Decision for Every App IdeaBuild 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 #mobilestrategy! 37  
  38. 38. 1.  Let the Mobile Use Case Drive the Decision2.  Availability of Development Skills3.  Maintenance and Support4.  Performance5.  Security 6.  Avoid Re-Litigating the Decision for Every App Idea
  39. 39. One More Consideration:The cost of doing nothingdue to “Analysis Paralysis”
  40. 40. Propelics Kickstarts Propelics & iTexico Special Offer Mobile App Free 1 Hour Mobile Scoping & Advisory Call Planning Kickstart 888-405-2820 Mobile App Mobile Mobile App IT Readiness Prototype Roadmap Center of Rapid for Mobile Factory Excellence Prototyping Kickstart #mobilestrategy! 40  
  41. 41. Thank you (Q&A) @propelics @itexico #mobilestrategy!
  42. 42. •  Innovation Focus•  Engaging Process•  Mobility Centric•  Experience Across Industries•  Enterprise Solutions•  Advisors, Strategists, Implementers•  Strategy at the Pace of Mobility