THE HYPE“HTML5 takes the internet bystorm”BBC News (Technology), 8 May 2012“New York Times and Burberry join theHTML5 brigade”The Guardian Technology Blog, 3 Oct 2012
… AND SOME ‘ANTI’-HYPE“Why HTML5 Is Still Not Ready ForPrime Time”Business Insider, 7 Nov 2012“The biggest mistake we made as acompany was betting too much onHTML5 as opposed to native”Mark Zuckerberg“Why LinkedIn dumped HTML5 & wentnative for its mobile app”Kiran Prasad
GARTNER HYPE CYCLEGartners 2012 Hype Cycle for Emerging Technologies
WHAT IS HTML5?
HTML5• Canvas and video tags• Local storage• Web Workers – background tasks• Web Sockets• CSS3 – layout, opacity, gradient fill …• And more ...
HTML5 FOR MOBILESmartphone sales exceed those of PCs for first time, Feb 2012
NATIVE vs. HTML5 vs. HYBRID• Native• HTML5– Accessed via the browser– Some phone features not accessible– App-like experience is possible (but not via app-store)• Hybrid– HTML5 content rendered within a browser control– Distributed through app-stores / marketplaces– Best of both worlds
HTML5 IS MANY THINGS
WHY LIMIT YOURSELF TO JUSTHTML5?
SELECTING A FRAMEWORK• Usual principles apply– Cost– Maturity– Support / community• What is the end-user experience?• What is the developer experience like?• How much code is shared?• Which platforms do I care about?… now go and start testing
Helping you select a cross-platform mobile framework… inspired by TodoMVC
• A realistic application• Create apps that are ready for app-storedistribution• Matches the native look and feel for eachplatform• Well designed / structured
JQUERY MOBILE – THOUGHTS• Some UX compromises• Android uses iOS theme– Android and iOS share the same code• Windows Phone experience was verywas poor• Some friction between frameworks• Tooling was ‘standard’ web approach
SENCHA TOUCH• Popular commercial framework• Built using Ext JS• An end-to-end solution• Creators of Fastbook
SENCHA TOUCH - THOUGHTS• ‘Thick’ UI abstraction – no HTML• Android and iOS use the same theme• Almost declarative feel to theapplication code• Impressive user experience• Steep learning curve• No Windows Phone support
XAMARIN• C# and the .NET framework• Very thin abstraction layer• MonoTouch and MonoDevelop• Native UI
XAMARIN - THOUGHTS• Matches the native experience exactly• More code – yet strongly typed• Lacks a UI abstraction layer• Planning is required to optimise codesharing– You could easily end up with zero codeshared
AND THE REST …• Adobe Air• jQTouch• RhoMobile• KendoUI• mgwt• Intel App Framework• DXTREME• Enyo• Emy
CONCLUSIONS• HTML5 is a viable technology• HTML5 is a route of compromise• HTML5 is not the only cross-platformtechnology
CHOOSING A FRAMEWORK• Determine what is important for yourapplication– Cost? UX? Which platforms?• Use PropertyCross to narrow the selection• Prototype your application• Evaluate– Code sharing– Developer experience– User experience