Flutter at scale-experience from 25+ Flutter Devs working together on a mobile banking app
summary
Built a production mobile banking app with 25+ Flutter devs inside a 200‑person project, using a multi‑package Dart repo and a single ownership map (markdown) so every package is owned by a team. CI uses Melos task runner for cross‑package scripts, a single lint package for consistency, and a dedicated technical team that maintains common libs. A component design system with 200 components, private style constructors, color‑scheme abstraction, and a Storybook web preview proves effective for dark mode and accessibility fixes.
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 1:24Code ownership strategies
- 5:38Defining code boundaries
- 10:03Modular project structure
- 12:50Tools for multi-package apps
- 14:18Design system foundations
- 17:12Implementing the design system
- 19:41Atomic design methodology
- 21:54Figma and development workflow
- 25:02Storybook for UI testing
- 29:05Conclusion and Q&A
related talks
44mMultimodule Flutter App
31mFlutter with 50+ Engineers
45mFlutter: A journey of productivity and happiness
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
35mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
37mLessons learned from crafting an in-house framework
37mFlutter at scale
36mFlutter Add-to-App: The Good, the Bad and the Ugly