The deck from my talk at the inaugural Emerging Tech Meetup at Cantina.
MOBILETools of theMOBILEweb
View Slide
NativeHybridMobile WebFrameworks
All-in-one frameworksSencha Touch too
Frameworks allow for quickdevelopment of mobile apps.Place Puppy MobilePuppiesSlideSlide UpList of PuppiesAnother List of Puppies© 2012 Place PuppyNo Sencha Touch example could fit in a slide.
Frameworks are great forquick development, but...
...framework appsjust never feel right.
If an app looks native, itshould perform natively.
Framework experiencestend to be choppy...
...and their scrolling sucks.
If you’re going with theweb, embrace the web.The good & bad parts.http://cri.st/EUli
It’s possible to use a frameworkwhile embracing the web.http://bagcheck.com
HybridMobile WebFrameworksà la carte
50% of mobile users abandonafter 6-10 seconds.
Server ResponseProcessing+Page time
Every library addsprocessing time.
Backbone.jsSammy.jsSpine.jsJavscript MVCAgility.jsKnockout.jsAngular.jsEmber.jsEyeballs.jsClient side MVC...
... can be overkill.Handle with care.
Micro libraries can ensure youonly use what you need.jQuery Zepto Zesthttp://cri.st/EdMnhttp://zeptojs.com/> >
Ender.js helps too...“Build only what you need, whenyou need it.”
http://microjs.com/
~92% of mobile is webkit...
...build if it were 0%
Replace JavaScriptanimations with CSS3...
...fall back to Javascript ifyou have to.
CSS3’s translate3d utilizeshardware acceleration..selector {transform: translate3d(0,0,0)}
Use local storage to cache tomaximize performance.window.localStorage.set(‘something’, variable);
Cache manifest in HTML5 canreduce calls to the server....CACHE MANIFESTpuppy.htmlpuppy.cssjquery.min.jspuppy.jspuppy.htmlpuppy.appcache
Mobile WebFrameworksà la carteResponsiveDesign
Great for contentsites and some apps.
Doesn’t solve 100% ofthe problem.
Use responsive principalsfor device targeted sites.
Frameworksà la carteResponsive DesignFin.