Building Flutter apps in Lego style
summary
A concrete pattern for modular Flutter apps: each feature is a Dart package with a flow entry point (a tiny widget that initializes DI, localization and internal navigation), feature-private src and exported abstracts for app-level implementations. The sample app has Lego worlds and a Harry Potter flow, uses get_it + injectable for DI, flow_builder for internal navigation and go_router for external routing, recommends Mason templates and build_yaml for codegen, and claims 95% coverage with Gherkin-style feature tests for real integration-like verification.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:11Lego modularity inspiration
- 4:25Decomposing app into modules
- 7:58Domain layer in features
- 10:04Dependency injection setup
- 12:37Feature configuration
- 14:44Localization strategy
- 16:51UI and state management
- 19:22Design system essentials
- 20:47Internal vs external navigation
- 23:58Feature entry point flow
- 25:22Testing approach
- 27:54Project structure demo
- 29:17Managing many packages
- 31:27Benefits of modularity
related talks
09mFlutter for Enterprise: How your company should be building with Flutter at scale
27mBuilding with best practices in FlutterFlow
37mLessons learned from crafting an in-house framework
44mBuilding Pieces for Developers Our Journey with Flutter and Dart
28mBuilding a Flutter App for Ubuntu
50mFlutter in Action: How to build cross-platform app with Dart
50mFlutter: The Wizards of Widgets
30mCat-like Development: Flutter for Efficiency