Why we failed at modularizing our app. An honest retrospective.
summary
Sky attempts to modularize a multi-flavor Android app and fails first because the team uses flavors to share code, picks the wrong first modules (streaming is tightly coupled, splash screen is worthless), and misuses Dagger causing cyclic dependencies and fragile singletons; a failed showcase app wastes time. The recovery is concrete: break features into black-box modules, treat modules as libraries, create a sample app per module, integrate early, use resourcePrefix to avoid collisions, and keep dependency injection and interfaces simple.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 7:30Flavors and legacy architecture
- 13:53First modularization attempt
- 20:14Dependency injection pitfalls
- 24:52Keep it simple principle
- 28:08Overcomplicating modules
- 30:14Testing and showcase app
- 33:02Resource conflicts and scoping
- 36:16Key takeaways and advice
- 38:01Q&A and closing
related talks
39mWhy we failed at modularizing Sky Sports. An honest retrospective.
32mBuild a modular Android app architecture
40mModularizing Android Applications
32mRoad to modularization
20mBreaking Down Modularization
27mModularising the right way
34mIntro to App Modularization
34mModular Flutter App Architecture Answering the What, When and How