Spotify Encore Architecture
Spotify Encore DS 3-layer architecture (engineering.atspotify.com): Foundational (tokens, primitives) → Style (CSS+vars, themed) → Behavior (logic, interaction). Separates what changes fast (style/branding) from what does not (foundational primitives). 2026 stack: headless React ARIA + Base UI + internal MCP server to expose Encore to Spotify multi-team agents.
Strengths
- Separates what changes fast (Style, branding) from what does not (Foundational), refactor savings
- Replicable multi-device and multi-brand without duplicating the whole stack, unique Foundational
- Agent-ready integrated in 2026: Spotify has an internal MCP server exposing Encore to 200+ devs
Limitations
- Heavy upfront investment, 3 cleanly separated layers require senior DS teams and several quarters
- Partial Spotify documentation, no public repo to clone, it is a blueprint, not a kit
Best for
- Streaming/media multi-device DS managers wanting a proven blueprint for 4-6 sibling DS
- Multi-brand retail (parent + 5 sub-brands) needing to separate the common (Foundational) from the specific (Style)