![]() ![]() #Spotify color palette based on my music plus#It’s where we keep things like color, type styles, motion, spacing, plus guidelines for writing and accessibility. Encore FoundationĪt the center, we have Encore Foundation. Here's what Encore looks like under the hood. Before, we had 22 disconnected design systems now, we still have multiple systems, but they’re all connected and under the same umbrella. The different systems stay connected because they’re all built using design tokens, and they live on the same website, following a similar structure defined by the Encore framework. We’ve either straight-up rebranded them or extracted parts of them to create the new Encore systems. The framework is new, but Encore actually reuses a lot of the great that went into our previous design systems. So is Encore Spotify’s “new design system”? Not exactly. And while these teams maintain the different systems, anyone who builds products at Spotify can contribute. There are several design systems inside Encore, each managed by a different team around the company. Most importantly, we wanted a system that would fit with Spotify’s culture of autonomy-one that could scale across multiple platforms and use cases. We wanted to consolidate the resources we had, and create a system that felt unified, accessible, collaborative, and based on a coherent vision. We weren’t starting with a completely blank slate, though. This time, we wanted to design our design system, just like we’d design one of our product experiences. So, in 2018, we kicked off a new effort to create a design system for the company. Spotify really needed a useful, unified design system-but we knew that a centralized team like GLUE probably wouldn’t work. Can you imagine being a new designer or engineer and asking, “Hey, do we have a design system?” and the answer is, “Yeah, we actually have 22”? Pretty confusing. At one point, we counted 22 different design systems floating around. But this extremely decentralized, “everyone make your own” approach wasn’t sustainable. ![]() We wanted to make it possible for listeners to access Spotify anywhere.Ī lot of great work went into these ground-up efforts, and we’re still using parts of these systems today. This was in part due to a new company strategy: ubiquity. Now we were also designing for cars, smartwatches, speakers, and even smart fridges. The days of designing for mobile and desktop were long gone. In 2018, Spotify continued to grow, and fast. After a while, we saw that having a centralized design systems team didn’t fit with this way of working. Spotify values “aligned autonomy” and empowers teams (squads) to make their own decisions. Why? It comes down to how the organization is set up. ![]() This was great for consistency, and many companies find that a centralized team works for them. The team refreshed Spotify’s look and feel, standardized many of our components across mobile and desktop, and grew from a handful of people to 30+ full-time engineers and designers.īut there was a catch: GLUE was a single, centralized team. The GLUE design system was a success in lots of ways. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |