Look up Javascript on mobile
summary
Claim: heavy client templating and naive event handlers kill mobile performance so move HTML rendering server side with a render=true flag, avoid big client JSON parsing, and move compute into web workers. Built a tiny library called eventman that attaches capture‑phase listeners on body, assigns node IDs and stops propagation; testing shows firing 1,000 delegated events drops from ~300 ms (old jQuery) to ~33 ms. Avoid inline handlers, document.fragment and JS animations on low‑end devices.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:30Introduction
- 7:53Browser Design
- 8:44Ui
- 11:35How Can You Optimize Your Javascript on Mobile
- 12:14Why You Use Javascript on Mobile
- 12:29Animations
- 16:14Events
- 16:52What Makes Events Heavy
- 17:40Capture Phase
- 19:35Dom Channel
- 32:45Out of Scope Exit
- 33:16Localizing Variables
related talks
32mResponsible Javascript
41mBrowser Internals for JS Devs
40mMaking the Jump: How Desktop Era Frameworks can Thrive on Mobile
39mYou really don't need all that JavaScript, I promise
41mYou Really Don't Need All That JavaScript I Promise
19mPocket-sized JS
21mYou Really Don't Need All That JavaScript, I Promise
30mDefying Facebook: Creating High Performance Mobile Apps