Coupang Android Architecture Part 1
Article Summary
Joris Abale from Coupang reveals how they rescued a massive Android app drowning in God Activities and Fragment chaos. Their journey from architectural debt to 80% test coverage is a masterclass in pragmatic refactoring.
Coupang, one of Korea's most popular apps with 10 million users, faced a codebase crisis in 2016. Years of rapid feature development had created unmaintainable God Classes, complex fragment lifecycles, and mounting technical debt. The engineering team needed a systematic approach to modernize without disrupting their customer experience.
Key Takeaways
- Chose MVP over MVVM because Google's data binding was still beta
- Integrated SonarQube into CI pipeline to track code quality metrics
- Built custom MVP library to reduce boilerplate and ensure consistency
- Achieved 80% unit test coverage after months of systematic refactoring
- Adopted Google's lifecycle aware components when they launched in 2017
Coupang successfully refactored their entire Android codebase to MVP architecture while maintaining service to millions of users, proving large scale modernization is possible with the right strategy.
About This Article
Coupang's Android app had real issues with how fragments and activities talked to each other. The lifecycle management was messy, and fragments kept growing into God Fragments even after the team tried to break them up. This left them with a lot of technical debt spread across millions of lines of code.
Coupang looked at MVC, MVP, and MVVM to figure out what would work best. They went with MVP because it was easier to test and could be integrated without relying on beta libraries. Then they built their own MVP library to make presenter binding consistent and cut down on boilerplate code.
Adding SonarQube to their CI pipeline helped Coupang find and remove duplicate code and reduce overall app complexity. Their metrics dashboard tracked the steady decrease in code issues over time.