How We Release the Spotify App: A Look Under the Hood (Part 2)
Article Summary
Spotify's release managers were drowning in Jira tabs, juggling dozens of tickets while fielding Slack questions. One dashboard changed everything.
In Part 2 of their release series, Spotify's engineering team reveals the custom tooling they built to orchestrate releases across Android, iOS, and Desktop. This is a deep dive into the Release Manager Dashboard and the automation that powers their multi-platform release process.
Key Takeaways
- Unified 10+ data sources into single dashboard, cutting context switching dramatically
- Backend optimization reduced load time from minutes to 8 seconds
- Release automation robot saved 8 hours per release cycle on average
- Built on Backstage with React/TypeScript for seamless developer integration
- Color coded status (green/yellow/red) enables instant release health assessment
By building a custom Release Manager Dashboard and automation robot, Spotify reduced their average release cycle by 8 hours while eliminating the chaos of managing releases across multiple tools.
About This Article
The Release Manager Dashboard backend was slow and expensive. Every time someone reloaded the page, it triggered massive data queries across 10 different systems, which meant long load times and high operational costs.
Spotify fixed this by adding caching to the backend service and pre-aggregating data every five minutes. They also simplified the API gateway so it could pull release data from multiple sources and present it through a single, consistent interface.
Load time dropped to 8 seconds. Operational costs fell dramatically, from what used to be expensive to almost nothing. The dashboard is now fast, reliable, and cheap to run.