<- Back to Blog

Spotify: Decentralised approach to evolving design systems

nouman-tariq
Nouman Tariq ยท
Spotify: Decentralised approach to evolving design systems

This blog post from the design engineering team at Spotify is a gem for all design system enthusiasts and techies alike. Marina Posniak, Gerrit Kaiser, and Shaun Bent take us on a journey through the evolution of design systems at Spotify.

The challenges faced by Spotify's older design system, GLUE, centered around its centralized nature, which clashed with the company's commitment to "aligned autonomy". While GLUE successfully standardized visual design, it became a bottleneck as Spotify expanded. The evolving company strategy, emphasizing ubiquity across various platforms, underscored the need for a more scalable and adaptable design system, prompting Spotify to explore a decentralized approach with the development of Encoreโ€”a family of design systems managed by distributed teams.

Diagram from the blog showcasing how Encore is structured where each system depends on Foundation and each system contains code, design and documentation

Kudos to the team for not just introducing Encore as a new design system but for brilliantly reusing the best aspects of their previous systems. The article effectively communicates how Encore is not a monolithic entity but a dynamic framework, a "system of systems." The use of design tokens to connect various components and the focus on maintaining connectivity while allowing autonomy to different teams is commendable.

This post is a testament to how the team at Spotify is actively solving design challenges and adapting to the ever-evolving landscape, setting a great example for the industry.

Read the original article
design systems
system of systems
decentralised

We are constantly adding cookbooks for design systems.

We are engineers working in design systems that impact millions of people. Meet the team folks behind this platform and read why we do this.