Native VS Hybrid
Mobile Apps
Senthil Kumar
senthil@indix.com
About me
• Mobile App Developer @ Indix
• Working on iOS & Android apps.
• Ex- Ness employee – Bangalore.
• Worked on EPL ...
Agenda
• Magic Quadrant for Mobile
• Native Platforms
• Advantages & Disadvantages of Native Approach
• Hybrid Apps
• HTML...
Magic Quadrant for Mobile Application
Development Platforms
Android vs iOS
Native Apps
• User prefers native apps
- 80 % of time is spent on apps and 20 % on
browsers(Flurry report)
• High User Eng...
Languages &
Environment
What Stops from using
Native?
• Platform dependent – code can’t be
reused
• Multi skill set and tool requirement
• Higher ...
Hybrid Apps
• It’s a bridge between Native and Web
Apps
• Cross platform reach is more
• Instant products update
• Data gu...
HTML5 routes to Market
Issues with Hybrid Apps
• Performance issues
• Lack of multithreaded strategy
• Problem with DOM manipulation and layout
•...
Adobe PhoneGap
• Cross platform reach is more
• Supports jQuery mobile, Backbone.js, Bootstrap
from twitter, Angular.js an...
Mix up Native & HTML
A good cross-platform application looks at home on whatever platform it is
used on. A bad cross-platform tries to look ide...
Myth VS Reality
Swap??
Mobile @ Scale
• Focus on Speed
• Experimentation for all
• Measurement
• Scaling teams
• Scaling Applications
• Motion De...
LinkedIn – Why they dumped
HTML5?
• Lack of debugging and performance tools
• Lack of runtime diagnostics information
• Hi...
Facebook
• Initially FB built mobile app using HTML5 and
javascript in a native wrapper, a hybrid
solution.
Why FB went Na...
Dropbox
• Share client side code across platforms
• Client code was written in C++
• Mostly data layer, sync, cache etc.
•...
Questions?
Thanks!
Native vs hybrid approach Mobile App Development
Native vs hybrid approach Mobile App Development
Native vs hybrid approach Mobile App Development
Native vs hybrid approach Mobile App Development
of 26

Native vs hybrid approach Mobile App Development

Native vs Hybrid Mobile app development. Challenges. Advantages Cross platform evolution
Published on: Mar 3, 2016
Published in: Mobile      
Source: www.slideshare.net


Transcripts - Native vs hybrid approach Mobile App Development

  • 1. Native VS Hybrid Mobile Apps Senthil Kumar senthil@indix.com
  • 2. About me • Mobile App Developer @ Indix • Working on iOS & Android apps. • Ex- Ness employee – Bangalore. • Worked on EPL football apps & ATP Tennis mobile apps.
  • 3. Agenda • Magic Quadrant for Mobile • Native Platforms • Advantages & Disadvantages of Native Approach • Hybrid Apps • HTML5 Approaches & Key Players • HTML5 Myth VS Reality • Adobe – PhoneGap • Mobile @ Scale • Case Studies – LinkedIn, Facebook & Dropbox • Conclusion
  • 4. Magic Quadrant for Mobile Application Development Platforms
  • 5. Android vs iOS
  • 6. Native Apps • User prefers native apps - 80 % of time is spent on apps and 20 % on browsers(Flurry report) • High User Engagement & Smoother Experience • Faster adoption to support new OS Versions • Offline support and Hardware access • Monetization
  • 7. Languages & Environment
  • 8. What Stops from using Native? • Platform dependent – code can’t be reused • Multi skill set and tool requirement • Higher TCO (Total cost of ownership)
  • 9. Hybrid Apps • It’s a bridge between Native and Web Apps • Cross platform reach is more • Instant products update • Data guides them on future decisions (A/B testing)
  • 10. HTML5 routes to Market
  • 11. Issues with Hybrid Apps • Performance issues • Lack of multithreaded strategy • Problem with DOM manipulation and layout • Memory Management • Lack of debugging tools
  • 12. Adobe PhoneGap • Cross platform reach is more • Supports jQuery mobile, Backbone.js, Bootstrap from twitter, Angular.js and so on…
  • 13. Mix up Native & HTML
  • 14. A good cross-platform application looks at home on whatever platform it is used on. A bad cross-platform tries to look identical everywhere
  • 15. Myth VS Reality
  • 16. Swap??
  • 17. Mobile @ Scale • Focus on Speed • Experimentation for all • Measurement • Scaling teams • Scaling Applications • Motion Design
  • 18. LinkedIn – Why they dumped HTML5? • Lack of debugging and performance tools • Lack of runtime diagnostics information • High crash rates due to memory exhaustion • Animations and spinners smoothness are not great
  • 19. Facebook • Initially FB built mobile app using HTML5 and javascript in a native wrapper, a hybrid solution. Why FB went Native? - Better touch tracking support, especially on Android. - Smoother animations are always an asset. - Better caching. - AppCache is soooooo busted we stopped using it
  • 20. Dropbox • Share client side code across platforms • Client code was written in C++ • Mostly data layer, sync, cache etc. • Build a library – use it for Android and iOS
  • 21. Questions?
  • 22. Thanks!

Related Documents