Javascript's comeback story on Mobile
summary
Claims that Famo.us rendering engine replaces the browser render tree with a game‑style physics and matrix transform pipeline and achieves smooth animations at 60 fps, backed by examples: a CRM app with scroll view, rotating logo and activity feed, wrapped with PhoneGap on iOS and integrated with RequireJS and Backbone. Performance notes include tradeoffs for Android WebView, use of web workers, a suggested renderable budget of 500–2,000 renderables, and that CoSight.io actually bets its startup on Famo.us.
AI-written summary · about
chapters (15)
- 0:00Start
- 3:47Options for a unified codebase
- 5:20Wrapper should contain the latest browser features
- 7:44Layout thrashing: an example of DOM inefficiency
- 9:37Basics - perspective transformation
- 10:07Famo.us is a high-performance Ul layout engine with its own animation and physics engine
- 11:21Planning out your Render Tree
- 13:15Spinning Logo
- 14:40Tab Transitions
- 17:18Features needed to build a high-quality app
- 18:19Modularity - Require.js
- 19:47Create models, collections in Backbone.js
- 21:08Responsiveness - minimize work on UI thread
- 21:42Use wrappers to utilize more powerful browser engines
- 26:46Summary
related talks
32mThe browser kicked me out (of the CPU): Making a three.js WebGL mobile game
30mDefying Facebook: Creating High Performance Mobile Apps
48mMobile Apps with JavaScript - There's More Than Web
40mJS performance in mobile web and hybrid apps… because science!
37mHTML5 Game Engine development
25mThe Web: Evolution in Action
51mWrite once, run everywhere: ambitious cross-device web apps
32mDone in 0.0166666666 seconds