"But does it scale?"
summary
Company app grows from four Flutter developers with 430 Dart files and 14 tests to a 19-developer team with 10x Dart files and 100x test files, reaching 187 packages in a monorepo. CI/CD uses Melos, Mason, GitHub Actions, Docker, Fastlane and Codemagic; UI tests run as headless Linux apps generating screenshots, histograms detect design-system migration regressions, and selective module testing plus sharding keeps checks to CI under 5 minutes. Result: feature velocity moves from months to weeks and scaling holds so far.
AI-written summary · about
chapters (8)
- 0:00Introduction to scaling
- 2:08What scaling means
- 8:38Testing strategies for fear reduction
- 12:55Design system lessons learned
- 17:10Code structure and modularization
- 21:44Automating release processes
- 27:12Continuous integration best practices
- 31:53Conclusion and final thoughts
related talks
35mIt Scales Until It Doesn’t
43mThe exciting adventure of scaling a mobile application
49mSoftware Architecture, Team Topologies & Complexity Science
11mInterview with Kamil Klyta & Wiktoria Sobczyk
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
27mScaling Your Front-End in a Realistic Way!
53mKeynote - Software Architecture, Team Topologies and Complexity Science
25mHow Hard Can a List Be? A Tale of APIs, Perf, and People