Native vs hybrid approach Mobile App Development

Download Native vs hybrid approach Mobile App Development

Post on 23-Aug-2014

92 views

Category:

Mobile

12 download

DESCRIPTION

Native vs Hybrid Mobile app development. Challenges. Advantages Cross platform evolution

TRANSCRIPT

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 football apps & ATP Tennis mobile apps. 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 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 Engagement & Smoother Experience Faster adoption to support new OS Versions Offline support and Hardware access Monetization Languages & Environment What Stops from using Native? Platform dependent code cant be reused Multi skill set and tool requirement Higher TCO (Total cost of ownership) Hybrid Apps Its a bridge between Native and Web Apps Cross platform reach is more Instant products update Data guides them on future decisions (A/B testing) HTML5 routes to Market Issues with Hybrid Apps Performance issues Lack of multithreaded strategy Problem with DOM manipulation and layout Memory Management Lack of debugging tools Adobe PhoneGap Cross platform reach is more Supports jQuery mobile, Backbone.js, Bootstrap from twitter, Angular.js and so on 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 identical everywhere Myth VS Reality Swap?? Mobile @ Scale Focus on Speed Experimentation for all Measurement Scaling teams Scaling Applications Motion Design 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 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 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 Questions? Thanks!