Platformizing features at Spotify
summary
Spotify refactors the Now Playing and Podcast show page into standalone components and a modes system so teams register a mode (podcast, music, video) and compose or replace components instead of editing monolithic code. A custom unidirectional state tool called Marvelous manages per-component state (pure update functions, effects). Result: support time drops from ~30% of a team’s effort, new experiences (audiobooks) ship without blocking owners, testing and debugging improve; platform runs inside a 1.5M-line app with ~1,000 commits/week and 450M MAUs.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 2:52Problem with now playing view
- 5:00Splitting into reusable components
- 6:26Introducing modes for extensibility
- 10:45Why this approach worked
- 13:55Podcast show page refactor
- 16:22Marvelous state management tool
- 18:10Lessons learned and recommendations
- 19:13Q&A session
related talks
27mShifting Spotify Engineering from Spreadsheets to Backstage
19mHigh Performance Backstage for High Performing Organizations
36mModularization - How hard can it be?
43mMobius-Loopy UI Architecture
41mMODULARIZATION HOW HARD CAN IT BE
20mSpotify's Growth Exposed the Abstraction Paradox
40mScalable JavaScript architecture
23mScaling the Sound: Fleet Management at Spotify