A Behind-the-Scenes Look at How We Release the Spotify App (Part 1)
Article Summary
Spotify ships weekly releases to 675 million users across iOS and Android. Here's how they balance speed with quality at that scale.
The Spotify Release team pulls back the curtain on their mobile release process. They manage hundreds of changes per week while maintaining strict quality standards through a dedicated Release Manager and custom tooling.
Key Takeaways
- Weekly release cycle: from Friday branch creation to 100% rollout in 10 days
- Trunk-based development with feature flags for major changes like Audiobooks
- Release Manager Dashboard tracks crashes, ANRs, blocking bugs, and test status
- Two-phase rollout: 1% initial deployment, then 100% after validation
- 95% of releases reach all users without cancellation
Spotify's structured 10-day release cycle and custom dashboard enable weekly app updates to hundreds of millions of users while maintaining quality gates.
About This Article
Spotify pushes out hundreds of code changes every week to 675 million users across different devices and regions. This creates a real tension between moving fast and keeping quality high. When serious bugs hit, like crashes during signup or playback, they need to be fixed right away.
Spotify set up a 10-day release cycle using trunk-based development and feature flags for big changes. A dedicated Release Manager coordinates across teams with a custom dashboard that watches blocking bugs, crash rates, and ANRs as they happen.
Over 95% of releases now roll out to all users without getting cancelled. The weekly pace lets teams fix smaller bugs in the next cycle and ship new features like Audiobooks faster. Quality checks stay in place across iOS and Android.