Architecture First: Foundations for Long Term Success
summary
A Flutter mobile app for collaborative spreadsheets (ZoTables) runs from a ~1M‑line codebase where added engineers onboard without docs and features remain independent, claiming long‑term stability. Practical patterns shown: proxy debugPrint + log dump that attaches to user feedback and captures onError/platformDispatcher stacks, code_mod injecting logs to add or strip trace calls, mixins for connectivity and lifecycle, a custom StreamController.broadcast event bus, navigator key/onGenerateRoute centralization, theme extensions and Bloc-aligned state flows.
AI-written summary · about
chapters (11)
- 0:00Architecture foundations
- 1:08Flutter architecture benefits
- 2:12Logging system setup
- 4:02Automating log insertion
- 6:16State propagation with mixins
- 9:50App links handling
- 11:16Event bus for updates
- 13:33Root navigation keys
- 16:46Theme management
- 19:49State management with BLoC
- 21:12Q&A
related talks
40mArchitecture: The LeanCode Guide
46mHow to Cook Flutter Properly
13mBuilding platform adaptive apps
31mFlutter with 50+ Engineers- 46mHow to Cook Flutter Correctly
19mA humble approach to Flutter app architecture
44mMultimodule Flutter App
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases