FOWA 2012: Native, HTML5, and Hybrid Mobile App Development: Real-Life Experiences - Eran Zinman

< my real life experience > Native, HTML5 & Hybrid Mobile Development Eran Zinman @ zzeran eran @conduit.com

ABOUT ME Manages R&D in Conduit Mobile

Mobile App DevelopmentHTML5 NATIVE HYBRID Objective C, Java, Native code +CSS / HTML / JS C# / XAML, C++ HTML5

Chapter 1 theBIG BANG

Chapter 1 Product requirements: • Cross-platform Native app • Mobile web app • Web Simulator • Small, agile team The solution: • Cross platform, cross browser HTML5 native app & web app

Chapter 1Initial POC Technologies: • PhoneGap 0.7.1 • jQTouch beta / jQuery LOOKING GOOD! POC included: NOT SO FAST… Design app in HTML / CSS Native features (PhoneGap) RESTful services (ajax) iPhone + Android

Chapter 1First RealProblem Scrolling × No support for “position: fixed” × Can’t place fixed position elements Alternative scrolling • iScroll.js (3.7.1 ?!) • 11K lines of Javascript code (yikes …)

Chapter 1Inconsistentexperience All browsers WebKit based, but: × No H/W acceleration × Slow performance × Render breaks × Missing events × Memory problems

Chapter 1 SUMMARY HTML5 Native The Good The Bad • Cross platform dev. / bug fixes • Bad performance on Android • New features are easy • Bad performance on BlackBerry • New platforms are easy • Same UI for all platforms • Small, agile team (2 dev.)

Chapter 2AndroidPerformance

Chapter 2 Problem: Slow scrolling performance Native UI Solution: Move fixed position elements to native UI WebView WebView Needed to create a 2 - way bridge Native Tabs HTML5 Native

Chapter 2 Problem: Slow page transition Solution: Use native code to make the transition, by taking a screenshot and moving the webview underneath

Chapter 2 SUMMARY HTML5 Native The Good The Bad • Smooth Android exp. • Bad performance on BlackBerry • Good iPhone exp. • Some spaghetti code • Dedicated Android dev.

Chapter 3The Eraof theWindowsPhone

Chapter 3 VERY UNIQUE UI but… 7.0 × No HTML5 and CSS3 × No H/W acceleration × No touch events

Chapter 3 WE NEED TO RETHINK OUR STRATEGY Moving to Cross Platform MVC (BackBone.js) Javascript HTML / CSS Data Business Views Models Logic C# / XAML Views

Chapter 3 SUMMARY HTML5 Native The Good The Bad • Good, native WP7 exp. • The pain of cross platform dev. • Separated WP7 solution • Dedicated WP7 developer

Chapter 4 This what we do now NATIVE UI Services Cache Notifications Logic Core Settings Usages Data Models Login Objective C Java C# HTML5 / CSS

Chapter 4 SUMMARY HTML5 Native The Good The Bad • Smooth UI • Big team, dedicated dev. • Doesn’t rely on browser render • New features are hard • Core sharing • Platform specific bugs

Let’s have a lookat the big players

iPad• One of the best HTML5 hybrid apps• Native / HTML5 combined UI• 4MB of minified JS / HTML / CSS• Same code for web / native• Different Web / Native UI per platform• Great engineering blog http://engineering.linkedin.com/blog HTML5 Native

iPad• Native → HTML5 → Native• Server based HTML / JS / CSS• Same code for web / native• App got bad reviews, very slow• Android is next to move to native UI HTML5 Native

SUMMARY HTML5 vs. Native is not just about technology. Development is an ongoing process, you can make amendments along the way and adjust your product. Don’t be afraid to experiment and admit you were wrong!

< / Thank you > Questions?about.me/eranzinman eran@conduit.com @zzeran Eran Zinman

http://lanyrd.com	84
https://twitter.com	63
http://eventifier.co	35
http://goh5.com	10
https://si0.twimg.com	4
http://www.linkedin.com	3
http://www.twylah.com	2
http://mobilewebpagedevelopment.com	2
http://www.eventifier.co	1

FOWA 2012: Native, HTML5, and Hybrid Mobile App Development: Real-Life Experiences - Eran Zinman

by Eran Zinman on Oct 16, 2012

Accessibility

Categories

Upload Details

Usage Rights

9 Embeds 204

Statistics

FOWA 2012: Native, HTML5, and Hybrid Mobile App Development: Real-Life Experiences - Eran Zinman Presentation Transcript