Spotify App Release Management Dashboard

3 posts · Jun 2020 – Jan 2026

What this trail covers

Spotify's Release Manager Dashboard, a Backstage plugin, continues to evolve to centralize and streamline the mobile app release process. This iteration details the weekly release cycle for versions like 8.9.2, emphasizing the coordination between developer merges, alpha/beta testing, bug triage, and phased rollouts. The dashboard's role in providing real-time status, identifying blocking bugs, and assessing release readiness against key metrics (crash rates, test results, sign-offs) is highlighted.

All Spotify trails

Feb 2026How We Release the Spotify App: A Look Under the Hood (Part 2)This post details the evolution of Spotify's Release Manager Dashboard, a Backstage plugin, focusing on its tooling and backend service. It describes the transition from Jira-based management to a unified web page that minimizes context switching and cognitive load for Release Managers. Key features include track-specific data visualization (release state, blocking bugs, sign-off status, quality metrics), handling of unassigned bugs, and a 'Robot' component that automates advancement through release states (branched, RC, submitted, 1% rollout, 100% rollout). The backend service was optimized with caching and pre-aggregation to reduce load times and costs. The post also discusses the use of React and TypeScript, integration with Backstage's Software Catalog, and future plans for modularization and wider adoption.
Apr 2025A Behind-the-Scenes Look at How We Release the Spotify App (Part 1)This post details the weekly release cycle for Spotify's mobile app, focusing on version 8.9.2. It elaborates on the process from code merge to user rollout, including trunk-based development exceptions for major changes, the role of feature flags, the use of alpha and beta programs, and the critical function of the Release Manager Dashboard. The dashboard's key data points (blocking bugs, build status, crash rates, usage, distribution status) and their role in decision-making for release blockers and phased rollouts are explained. Specific attention is given to the Audiobooks feature rollout and the rigorous testing and sign-off process required before submission to app stores and phased rollout to users.
Jul 2020Leveraging Mobile Infrastructure with Data-Driven DecisionsThis post details how Spotify's mobile DevOps teams have adopted a data-first approach to improve decision-making and company productivity. It highlights the challenges of mobile app development with longer release cycles and phased rollouts, and how data collection, promotion, education (Data University), and ownership have led to better observability and monitoring. The post provides examples of using build time trends and Xcode version usage data to inform technical decisions, such as prioritizing Swift development and planning environment/API migrations. It emphasizes the iterative process of data-driven decision making, from planning to evaluation, and its impact on both technical teams and product managers.
Advertisement