Implementing a Design System for Glovo Customers

Helio: building a design system and a shared components library from scratch. 

By Victor Borisov, Software Engineer at Glovo.

As Glovo started to expand to new verticals and release more new features, it led us to have to develop a lot more new user interfaces. It involved many engineers and different teams. At that time we didn’t have a design system, and all of this caused a lot of frustration for the engineers: they had to reinvent the wheel across different apps, it was a big blocker for moving towards micro frontends, and developing new UI was taking a lot of time. I will talk about how we solved those problems, what unexpected challenges we faced, and what technical tricks helped us take it to the next level.

You can have too much of a good thing: bringing together multiple design systems at Glovo. 

By Juan Ignacio Molina, Engineering Manager at Glovo.

How can you provide a consistent UX for very different users (Customers, Couriers, Partners, etc) on all platforms (Android, iOS, and Web) in 23 different cultures with autonomous design and engineering teams? If that sounded like a lot, now do that with 4 different design systems.
Let’s talk about how at Glovo we embarked on a journey to finally have one way of delivering a button, a color, or anything else by unifying common UI patterns, embracing specific users’ needs and learning to coexist with multiple design systems at the same time.