The Fundamentals of Android Development at Revolut
Article Summary
Revolut's Android team ships features to 25+ million customers every Tuesday at 9am sharp. Here's how 100+ engineers coordinate releases across 70 autonomous teams without QA.
Revolut's engineering team pulls back the curtain on their Android development practices. From multi-module architecture to weekly release trains, they've built systems that let them move fast while serving millions of financial app users across multiple products.
Key Takeaways
- 70 autonomous teams split between Platform and Product streams
- Multi-module architecture with Api/Implementation pattern enables parallel builds
- Weekly release train: code freeze Tuesday, beta testing, staged rollout
- Zero QA engineers but comprehensive coverage via unit, integration, screenshot, UI tests
- Custom in-house analytics framework tracks user behavior without third-party tools
Revolut ships Android releases weekly to millions of users using modular architecture, feature toggles, automated testing, and a disciplined release process that doesn't rely on traditional QA.
About This Article
Revolut's Android projects are split across 100+ modules, and when Implementation modules depend on each other, builds slow down and dependencies become fragile. This happens while over 100 engineers work on multiple products at the same time.
Revolut split each feature into two modules: a lightweight Api module and a heavier Implementation module. Implementation modules only depend on the stable Api modules, which lets them build in parallel without waiting for each other.
Implementation modules can now build at the same time instead of one after another. Build times dropped noticeably, and the architecture keeps features stable across Revolut's retail, Business, and under-18 products.