Crash-Proof Flutter: Building Apps That Refuse to Die
summary
Claims a defensive architecture that cuts crash rates (examples cite apps hitting 90% crash‑free), shows concrete fixes for common villains like setState called after dispose, render overflows and native Signal 11 crashes, and uses exact tools: flutterError.onError, PlatformDispatcher, runZoneGuarded, Sentry/Crashlytics, address/thread sanitizers and didHaveMemoryPressure. Demonstrations include a safeSetState mixin, a three‑life “Phoenix” widget, network fault injectors, a state‑teleporter for migrations, a minimal memory mode and the Armor package on pub.dev for safeExecute and monitoring.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:09Crash villains in Flutter
- 8:09Global error handling
- 12:08Quantum state management
- 16:25Phoenix self-healing UIs
- 23:08Native crash defense
- 25:37Network chaos testing
- 28:49State teleportation
- 30:35Crash pattern analysis
- 36:53Platform resilience
- 38:59Armor package tips
- 40:28Q&A
related talks
40mThread by Thread: The Hidden Battle for Flutter Stability
36mSecuring Flutter Apps
13mMonitoring your Flutter app's stability with Firebase Crashlytics
38mFlutter: A Path of Vines and Flowers
43mDangerous Flutter... Or Not?
30mCat-like Development: Flutter for Efficiency
12mWatching a Flutter app crash
49mFirst Flutter, then Fly: Build Reactive & Performant Cross-Platform Apps