Why we failed at modularizing Sky Sports. An honest retrospective.
summary
Sky Sports tries and initially fails to modularize a monolith that supports multiple country apps using flavors break shared code and long build times. Dagger subcomponents create cyclic dependencies and brittle injection, so the team adopts a component dependency pattern and per‑module interfaces for provisioning. Start with high‑value modules, integrate them into the app early, provide one per-module sample apps instead of a single showcase, enforce resource prefixes with Gradle lint, and keep solutions simple and documented.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:59Who am I
- 1:50Common sense is not common
- 2:47Sky Sports
- 3:47Flavours
- 6:37The problem
- 7:31Changing things
- 9:48The vision
- 11:53What is a module
- 14:00Streaming
- 16:14Start with the easiest module
- 17:40Its gonna be ugly
- 18:43Dependency injection
- 19:42Dagger implementation
- 20:13Dont use things you dont want to understand
- 25:21Takeaways
- 33:17Resource Conflict
- 36:22Scopes
- 37:15Recap
related talks
39mWhy we failed at modularizing our app. An honest retrospective.
40mModularizing Android Applications
32mBuild a modular Android app architecture
32mRoad to modularization
20mBreaking Down Modularization
34mModular Flutter App Architecture Answering the What, When and How
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing
39mModularization techniques from monolithic to multi-packages app