JS performance in mobile web and hybrid apps… because science!
summary
Measured Cordova apps run inside a webview and pay real costs: Android Cordova shows much larger memory footprint and much slower startup (slow‑motion frames used to quantify launches). Webview bridge latency scales linearly but stays tiny for common payloads; a 5MB crossing is still ~300ms. DOM notes: layout thrashing causes ~4s vs 56ms by interleaving reads/writes; simpler DOMs and virtualization cuts memory from ~350MB to <100MB and makes scrolling fluid. Chrome DevTools, Nexus 9, heap snapshots and simple Cordova plugins produce these concrete, actionable numbers.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:10What is Cordova
- 2:47Performance
- 4:55Methodology
- 6:26Differences
- 7:12WebView Tax
- 7:40Memory Footprint
- 8:26Browser
- 8:37Cordova
- 9:31Memory
- 10:26iOS
- 13:06Data transfer time
- 15:10Simple vs complex DOM
- 18:56thrashing
- 21:18infinite scroll
- 23:48memory consumption
- 24:44CSS gradients
- 25:17Performance vs maintainability
- 27:37Garbage collector
- 28:09Garbage collector in action
- 30:17Single event handler
- 31:54Single event handler demo
- 35:24Switch statement demo
- 35:46Heap snapshot
- 39:10Destroy all unused objects
- 39:25Outro
