Welcome.@propelics@itexicoQuestions, Comments
to #mobilestrategyHTML5 vs. NativeApps: Demystifyingthe DecisionMaking Proce...
#mobilestrategy!Propelics Background – About Us•  15+ year track record•  Fortune 500 clients•  Global experience•  100% f...
•  Enterprise Mobile Strategy ServicesEnterprise Mobile StrategyMobile App PortfolioMobile App Scoping & PlanningIT Readin...
#mobilestrategy!iTexico Background – About Us4	  Your partner in building and managing mobile andtechnology solutions
Some...
What We DoApplicationStrategy &Architecture!UI/UX !Design!Cross-PlatformMobileDevelopment!Website & BackendDevelopment!Tes...
#mobilestrategy!Adam Bookman: Partner - PropelicsAdam has been the brains behindmany mobile product and programlaunches. H...
#mobilestrategy!Richard Dutra: VP Business Development - iTexicoRichard is a Silicon Valleyexecutive and entrepreneur whol...
#mobilestrategy!Agenda!•  Market Trends•  The HTML5 vs. Native Conundrum •  6 Considerations in deciding HTML5 vs. Native•...
By 2015, 70%of your customerinteractions will originatefrom a mobile device…”
Source:	  Gartner	  2011	  
2012 was the year ofplanning for mobile.
2013 is the year 
of action.

Source	  Yankee	  Group,	  2011	  and	  2012	  Transition from B2C toB2E and B2E2C!Drivers are beyond“BYOD”!Beyond Cost S...
The Mobile War is Over. 
The App Has Won.
Source	  Flurry	  Analy=cs,	  comScore,	  NetMarketShare	  

Source	  ReadWrite	  Mobile	  
Regardless of CIO need, it’s theexperience that creates the demand.#mobilestrategy!
#mobilestrategy! 15	  HTML5 or Native?

An uninformed decision canresult in considerable extraexpense, dissatisfied usersan...
Demystifying theHTML5 vs. NativeDecision
6 Key Considerations
1.  Let the Mobile Use Case Drive theDecision2.  Availability of Development Skills3.  Maintenance and Support4.  Performa...
#1. Let the Mobile UseCase Drive the Decision
Avoid Square Peg –Round HoleSyndrome
#1. Let the Mobile Use Case Drive the Decision – HTML5The site http://mobilehtml5.org/is a good resource that mapsspecific ...
22	  Intermittent ExperiencesLarge Diversity of Devices / OS(Public Facing or BYOD)Content Centric ConsumptionTraffic from S...
#1. Let the Mobile Use Case Drive the Decision – Hybrid23Pros!Mix Web Code with Native Wrapper!Less Code to Support Multi-...
24	  Accommodate Multiple PlatformsDeliver “App Store” ExperienceContent Centric ConsumptionDirect TrafficAbility to Utilize...
#1. Let the Mobile Use Case Drive the Decision – Native25Pros!Rich User Interface!Best App Performance!Most Secure!Hooks i...
26	  Heavily UsedNeeds to be FastUse of Device Features like Camera, Calendar, Notifications,Orientation, Shake, NFCUser Ex...
Resist the One-Size Fits AllTemptation
#2. Availability ofDevelopment Skills
#2. Availability of Development Skills29•  How many platforms & form factors will you decide to support? If you are planni...
#3. Maintenance andSupport
#mobilestrategy!#3. Maintenance and Support31	  Two factors complicate the situation forNative/Hybrid Apps over Web Apps.!...
#4. Performance
#mobilestrategy!#4. Performance33	  A central part of user experience isperformance of the application on the mobiledevice...
#5. Security
#mobilestrategy!#5. Security35	  Along with Performance, Security is one thebigger advantages Native Apps have over Webbas...
#6. Avoid Re-Litigatingthe Decision for EveryApp Idea
#mobilestrategy!#6. Avoid Re-Litigating the Decision for Every App Idea37	  Build a Framework for HTML5 vs. Hybrid vs. Nat...
1.  Let the Mobile Use Case Drive theDecision2.  Availability of Development Skills3.  Maintenance and Support4.  Performa...
One More Consideration:The cost of doing nothingdue to “Analysis Paralysis”
#mobilestrategy!Propelics KickstartsPropelics & iTexicoSpecial OfferFree 1 Hour MobileAdvisory Callinfo@propelics.com888-40...
#mobilestrategy!Thank you(Q&A)@propelics @itexico
•  Innovation Focus•  Engaging Process•  Mobility Centric•  Experience Across Industries•  Enterprise Solutions•  Advisors...
Upcoming SlideShare
Loading in …5
×

HTML5 vs. Native Apps: Demystifying the Decision Making Process

588 views

Published on

It’s now clear that mobile is the path consumer markets are leaning towards to utilizing mobile apps as their preferred way to conduct e-commerce. According to a study by Gartner, 70% of customer interactions will originate from a mobile device by 2015. More and more organizations are realizing that mobile can significantly impact their core business operations and are transitioning to a mobile-based strategy. Therefore, iTexico partnered with Propelics to deliver a webinar: "HTML5 vs Native Apps: Demystifying The Decision Making Process" Here we present the slides from the last webinar.

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
588
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
40
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

HTML5 vs. Native Apps: Demystifying the Decision Making Process

  1. 1. Welcome.@propelics@itexicoQuestions, Comments
to #mobilestrategyHTML5 vs. NativeApps: Demystifyingthe DecisionMaking ProcessApril 11th, 2013
  2. 2. #mobilestrategy!Propelics Background – About Us•  15+ year track record•  Fortune 500 clients•  Global experience•  100% focused on mobilefor the Enterprise•  San Jose, Boston,Pittsburgh2  Propelics creates mobile strategies and world class 
Apps for the Enterprise.

Trusted by companies like yours:
  3. 3. •  Enterprise Mobile Strategy ServicesEnterprise Mobile StrategyMobile App PortfolioMobile App Scoping & PlanningIT Readiness for MobilityBYOD and MDM StrategyInnovation through visualizationCenter of Excellence Creation•  Mobile Advisory ServicesMobile MentoringExecutive EducationSpeaking Engagements•  Mobile App DevelopmentUX DesignOnshore and Offshore App DevelopmentMobile App ArchitecturePrototype FactoryWhat We Do
  4. 4. #mobilestrategy!iTexico Background – About Us4  Your partner in building and managing mobile andtechnology solutions
Some of our clients:Collaboration!Technical!Expertise!Fast toMarket!IP!Protection! Value!
  5. 5. What We DoApplicationStrategy &Architecture!UI/UX !Design!Cross-PlatformMobileDevelopment!Website & BackendDevelopment!Testing & QualityAssurance!Deployment,Maintenance &Support!•  HQ in Austin,Texas•  Near shoreSoftwareDevelopmentCenter inGuadalajara,Mexico. •  Western RegionOffice in SiliconValley. •  Focus on ExtendedTeam As A Service(eTaaS)TM andCross PlatformMobile Solutions
  6. 6. #mobilestrategy!Adam Bookman: Partner - PropelicsAdam has been the brains behindmany mobile product and programlaunches. He has advisedcompanies on mobile strategies forBusiness as well as IT. He continues to be a “TrustedAdvisor” to some of the leadingbrands around the world. Adam isfrequent speaker at conferencesrelated to mobile.6  
  7. 7. #mobilestrategy!Richard Dutra: VP Business Development - iTexicoRichard is a Silicon Valleyexecutive and entrepreneur wholoves building startups and beingpart of ground floor companies. Hebelieves mobile will be the singlemost important device we own andits capabilities are endless. His mission is to empowerorganizations by helping themrealize their mobile strategies andtransforming them into meaningfulsolutions.7  
  8. 8. #mobilestrategy!Agenda!•  Market Trends•  The HTML5 vs. Native Conundrum •  6 Considerations in deciding HTML5 vs. Native•  Q&AMissed your topic? propelics.com/lets-talk!8  
  9. 9. By 2015, 70%of your customerinteractions will originatefrom a mobile device…”
Source:  Gartner  2011  
  10. 10. 2012 was the year ofplanning for mobile.
2013 is the year 
of action.
  11. 11. 
Source  Yankee  Group,  2011  and  2012  Transition from B2C toB2E and B2E2C!Drivers are beyond“BYOD”!Beyond Cost Savings!Organizations arebeginning to identify howmobile can impact theircore metrics!
  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. #mobilestrategy! 15  HTML5 or Native?

An uninformed decision canresult in considerable extraexpense, dissatisfied usersand poor performance andexperience.!
  16. 16. Demystifying theHTML5 vs. NativeDecision
  17. 17. 6 Key Considerations
  18. 18. 1.  Let the Mobile Use Case Drive theDecision2.  Availability of Development Skills3.  Maintenance and Support4.  Performance5.  Security 6.  Avoid Re-Litigating the Decisionfor Every App Idea
  19. 19. #1. Let the Mobile UseCase Drive the Decision
  20. 20. Avoid Square Peg –Round HoleSyndrome
  21. 21. #1. Let the Mobile Use Case Drive the Decision – HTML5The site http://mobilehtml5.org/is a good resource that mapsspecific HTML5 functions vs.different mobile browserversions ! 21Pros!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. 22. 22  Intermittent ExperiencesLarge Diversity of Devices / OS(Public Facing or BYOD)Content Centric ConsumptionTraffic from Search / SocialSecurity of Data at RestPrimarily Connected Access#1. Let the Mobile Use Case Drive the Decision – HTML5
  23. 23. #1. Let the Mobile Use Case Drive the Decision – Hybrid23Pros!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 thatby 2016, over 50% ofMobile appsdeployed by theenterprise will beHybrid.!
-Gartner Predicts Feb. 2013!
  24. 24. 24  Accommodate Multiple PlatformsDeliver “App Store” ExperienceContent Centric ConsumptionDirect TrafficAbility to Utilize More Native ControlsBetter Offline Support#1. Let the Mobile Use Case Drive the Decision – Hybrid
  25. 25. #1. Let the Mobile Use Case Drive the Decision – Native25Pros!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 theyare going to spend thenext two years decidingwhat the next hybrid appframework is. In themeantime there will havebeen an awful lot of iOSand Android apps built.”!!- James Governor – RedMonk!
  26. 26. 26  Heavily 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#1. Let the Mobile Use Case Drive the Decision – Native
  27. 27. Resist the One-Size Fits AllTemptation
  28. 28. #2. Availability ofDevelopment Skills
  29. 29. #2. Availability of Development Skills29•  How many platforms & form factors will you decide to support? If you are planning to build a Native App, pretty much each platformis going to need at least one developer.•  Chances of finding someone who is good at all threedevelopment platforms is extremely rare.•  Today, developers familiar with web technologies are moreabundant, easier and cheaper to hire than experienced Nativedevelopers.•  Experienced front end mobile web developers possess high in-demand skills.•  If you are going the Hybrid route, again, you are looking forsomeone with the above JavaScript knowledge and knowledgeof the platforms you are using.
  30. 30. #3. Maintenance andSupport
  31. 31. #mobilestrategy!#3. Maintenance and Support31  Two 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 WebApps, you don’t face these challenges; your users are alwaysusing the latest version!•  Develop an ongoing App Support Plan to protect yourinvestment!
  32. 32. #4. Performance
  33. 33. #mobilestrategy!#4. Performance33  A 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 sogreat that even non-technical users easily notice thedifference.!
  34. 34. #5. Security
  35. 35. #mobilestrategy!#5. Security35  Along with Performance, Security is one thebigger advantages Native Apps have over Webbased Apps.!!•  Source Code Visible!•  URL based Vulnerabilities!•  Data on Device!•  Data in Transit!
  36. 36. #6. Avoid Re-Litigatingthe Decision for EveryApp Idea
  37. 37. #mobilestrategy!#6. Avoid Re-Litigating the Decision for Every App Idea37  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 for99.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
  38. 38. 1.  Let the Mobile Use Case Drive theDecision2.  Availability of Development Skills3.  Maintenance and Support4.  Performance5.  Security 6.  Avoid Re-Litigating the Decisionfor Every App Idea
  39. 39. One More Consideration:The cost of doing nothingdue to “Analysis Paralysis”
  40. 40. #mobilestrategy!Propelics KickstartsPropelics & iTexicoSpecial OfferFree 1 Hour MobileAdvisory Callinfo@propelics.com888-405-282040  Mobile AppScoping &PlanningKickstartMobile AppRoadmapMobileCenter ofExcellenceMobile AppRapidPrototypingIT Readinessfor MobileKickstartPrototypeFactory
  41. 41. #mobilestrategy!Thank you(Q&A)@propelics @itexico
  42. 42. •  Innovation Focus•  Engaging Process•  Mobility Centric•  Experience Across Industries•  Enterprise Solutions•  Advisors, Strategists, Implementers•  Strategy at the Pace of Mobility

×