1. PRACTICAL MOBILE DEVELOPMENT Yohan Totting tyohan@thinkrooms.com @tyohan

2. NativeComparisonHTML5WinRich user experienceLostWinPerformanceLostWinMonetizationLostLostCross platform costWinDrawFragmentation challengeDrawLostDeveloper availabilityWinLostDistribution & UpdatesWinWinInnovation & AdoptionLostWinSecurityLostRef: http://thinkmobile.appcelerator.com/blog/bid/284174/Native-vs-HTML5-looked-at-objectively-the-debate-is-over 3. When I'm introspective about the last few years I think the biggest mistake that we made, as a company, is betting too much on HTML5 as opposed to native ... because it just wasn't there. Mark Zuckerberg CEO of Facebookhttp://techcrunch.com/2012/09/11/mark-zuckerberg-our-biggest-mistake-with-mobile-was-betting-too-much-on-html5/ 4. There are a few things that are critically missing. One is tooling support, having a debugger that actually works, & performance tools that tell you where the memory is running out. Kiran Prasad LinkedIns senior director for mobile engineeringhttp://venturebeat.com/2013/04/17/linkedin-mobile-web-breakup/#C1JD0uL8F2zwziD6.99 5. USE NATIVE IF Buildan app as a product Dependon specic feature from mobile platform Performance Youis a musthave enough budget 6. USE HTML5 IF Forrapid prototyping Information Focusbasis appon cross platform Minimalbudget 7. WHAT I GOT FROM HTML5? 8. CREATE PROTOTYPES IN DAYS VS MONTH 9. BIG COMMUNITY & LOT OF REFERENCES TO LEARN 10. CODE ONCE RUN EVERYWHERE 11. HARD TO DEBUG 12. ALTERNATIVE? 13. HYBRID APP 14. NATIVE COMPILED APPXamarinTitanium Appcelerator 15. XAMARINC# Programming Language 16. TITANIUM APPCELERATOROpen SourceAnalyticsCloud Backend 17. MVC DEVELOPMENT 18. TITANIUM STUDIO IDE 19. TIPS 20. MOBILE FIRST 21. RESPONSE IT IN 3 SECONDS 22. Average Speed3G4G244 KB/s756 KB/s 23. REDUCE DEPENDENCIES 24. REDUCE IMAGE DIMENSION 25. REDUCE CLIENT SIDE PROCESSING 26. THANKS Yohan Totting tyohan@thinkrooms.com @tyohan