Mastering Flutter Web
summary
Rewrote a 10-year-old mobile game in Flutter to use one shared codebase across Android iOS web, measured bundle sizes (HTML renderer ~380 KB transfer, CanvasKit runtime ~2.9 MB transfer) and found HTML DOM-heavy rendering caused jank, switched to canvas kit renderer for native‑like performance, added a preloader mechanism for assets and shader warmups, implemented device clustering to drop decorations for low‑end GPUs, and recovered playability while noting about 3% users blocked by WASM ad blockers.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 7:58Flutter web renderers overview
- 17:29Switching to Canvas Kit renderer
- 24:11Preloading assets for performance
- 28:02Fixing animation jank issues
- 32:38Future optimizations and improvements
- 37:38Summary and final thoughts
related talks
38mFlutter Web in action
31mFlutter. New Approach to Web Development
28mAMA with Brian Egan and Filip Hracek
42mFlutter everywhere — from Mobile to Web
22mInnovation and Trends in Flutter for web
13mLearn how Flutter enhances web apps
41mWhy is Flutter the mobile SDK developers deserve...
33mBeyond Mobile: Building Flutter Apps for iOS, Android, Chrome OS, and Web
