Defying Facebook: Creating High Performance Mobile Apps
summary
Claims that HTML5 can be made fast are backed by concrete fixes: low‑end Android and Chromebooks expose real limits, max texture size breaks whole‑screen transforms, and applying translateZ per‑item often restores smooth kinetic scrolling while a single-layer transform kills performance. Form input types and the History API behave inconsistently across Android and iOS so fallbacks or polyfills are necessary. A working example uses Kindo UI mobile to build a list with per‑item GPU hints; some vendor hacks (a sub‑millisecond transition on certain devices) are required.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 2:04Who are you
- 3:09Who am I
- 5:01Facebooks biggest mistake
- 6:04Reality of mobile
- 7:37Refrigerators
- 8:11Chrome OS
- 10:41Webkit
- 11:03Browsers
- 11:34Performance Issues
- 12:18Translate Z
- 12:55Problems with Translate Z
- 13:22Fancy scrolling
- 13:56Slower scrolling
- 14:26Max texture size
- 15:27Max texture size fix
- 15:46Vendors are onto us
- 16:41Galaxy S3
- 17:12Performance is not just speed
- 17:51HTML5 Forms
- 21:13Labels
- 22:36Android
- 23:27Hashes
- 23:49CSS
- 25:14Conclusion
- 25:40Code Example
- 28:46Burke Holland
related talks
48mMobile Apps with JavaScript - There's More Than Web
46mJavascript's comeback story on Mobile
40mLook up Javascript on mobile
40mJS performance in mobile web and hybrid apps… because science!
32mThe browser kicked me out (of the CPU): Making a three.js WebGL mobile game
54mThe Future of the Web-Apps
54mA Successful Cross Platform HTML5 Game, From Shaping To Shipping
18mWeb Movements in China