Multimodule Flutter App
summary
A Flutter engineering talk describing how to structure a large multi-module Flutter app worked on by more than 10 product teams (up to 14 teams / ~20 developers). It covers organizational and technical challenges—matrix feature teams, team independence, hiring juniors, independent releases per team, long-lived production maintenance, rapid iteration, and integration with legacy bank systems—and presents the speaker’s team experience and solutions for scaling Flutter in a big-company environment.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:11Monolith app problems
- 6:23Choosing modular architecture
- 7:28Modular dev principles
- 8:52Flutter module structure
- 13:14Module internals
- 16:45Navigation and routing
- 21:18Isolated module dev
- 24:56Three years of results
- 26:40Q&A
related talks
45mFlutter and a Large Project — Who Wins?
30mFlutter at scale-experience from 25+ Flutter Devs working together on a mobile banking app
01h 13mFlutter and a Million Lines of Native Code
31mFlutter with 50+ Engineers
09mFlutter for Enterprise: How your company should be building with Flutter at scale
32mTailoring Flutter Architectures for Team and Business Success
37mLessons learned from crafting an in-house framework
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases