Lazy Flutter performance
summary
Shows concrete results: naive single-child lists blow memory up (10 → ~15MB, 100 → ~80MB, 1,000 crashes) while ListView.builder keeps memory flat and scrolling smooth; demonstrates a 2D fix using InteractiveViewer.builder with visible-cell checks and measurable ~3x memory reduction vs naive; profiles with DevTools and uses a heavy Rive Marty asset to force stalls; builds a procedurally generated map that swaps a 3x3 tile ring and performs multi-scale simplification so zooming and endless panning remain responsive.
AI-written summary · about
chapters (14)
- 0:00Start
- 2:23Procedural Generation
- 4:15Profiling the Memory Impact
- 5:05Item Builder
- 6:45Naive Approach and the Single Child Scroll View
- 7:06Listview Builder
- 7:31Memory Snapshot
- 8:04Interactive Viewer
- 9:422d Example
- 10:21Interactiveviewer Builder
- 13:02Procedural Generation Example
- 13:31Performance Optimizations
- 14:02Not Load any Assets That Are Not on the Screen
- 17:57Documentation
related talks
38mDebugging performance issues with the Flutter DevTools
21mAdvanced Memory Management in Flutter
43mPerformant Scrolling Layouts With Slivers
40mFluttering at 60 FPS
44mNo More Jank: How to Keep Your Flutter App Smooth and Snappy
19mFight, Flight, or Fix? Winning the Legacy Flutter Challenge
06mLightning talk from Vivian Cromwell
46mFlutter: 60 Frames of AOT Badassery