Fight, Flight, or Fix? Winning the Legacy Flutter Challenge
summary
Team inherits a messy Flutter app grown from an MVP with no state management and ~80% of data in one Hive bucket. Using DevTools (performance, memory, repaint rainbow) uncovers jank and nearly double memory use; replaced SingleChildScrollView with ListView and added RepaintBoundary to cut repaints. App size comes from --analyze-size, crashes tracked with Sentry/Crashlytics, migration via dart migrate/dart fix and dart pub outdated, and a Riverpod bridge to Hive models enables incremental fight/flight/fix strategy.
AI-written summary · about
chapters (8)
- 0:00Legacy Flutter challenges
- 1:30Assessing legacy codebase
- 4:43Flutter DevTools debugging
- 7:55Updating deprecated code
- 9:18Monitoring crashes and leaks
- 10:21Fight, Flight, or Fix strategies
- 14:34Business needs vs technical debt
- 16:48Summary and tips
related talks
40mThread by Thread: The Hidden Battle for Flutter Stability
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
45mFlutter: A journey of productivity and happiness
41mCrash-Proof Flutter: Building Apps That Refuse to Die
19mLazy Flutter performance
49mDemystifying performance tune up in Flutter and Dart
38mFlutter: A Path of Vines and Flowers
40mMastering Flutter Web