Systemizing a map component has remarkably more constraints than your average button. These seemingly simple interactive labels must stand out against all terrains, densities and fixed buttons. Can combined with regions, exact locations, objects or stand on their own. Are required to be big enough to meet accessibility and tap target requirements and small enough to not block map interaction. And flexibly hold content for 1 destination address or 1,000+ scooters and adjust when zoomed… and more!!!
This is our attempt at an elegant solution for systemizing interactive map labels, or as we like to call them— Map Bubbles.
There are two bubble types to help users differentiate between areas and exact locations on the map. …
On the surface color seems simple, but getting 100+ designers and engineers to follow guidelines that are a part of literally everything they make is a huge undertaking. To put it in perspective: over 50% of Lyft’s design system team’s office hours, high visibility projects and inner team disagreements are color related. We’ve learned a lot over the past three years. It sure as hell ain’t perfect, but it’s working pretty well so far.
These are the constraints that defined the construction of our system and the top issues we commonly face:
A system constrained to AA accessibility for a complex product will be constructed differently from a system with no accessibility requirement for a simple one. …
Most design systems teams are lean and the expectations placed upon them are disproportionately large. Does improve the quality of all of the company’s 70+ products sound familiar? When we first started our system, our conversation with leadership around ownership felt a bit like the Lion King:
Foundational elements and reusable components? Definitely. Quality principles? Accessibility? Of course. Brand in product? Yup, that too. Sound? Localization? Road Safety? Yup, yup and yup. A successful system’s adoption rate scales faster than the teams resources, resulting in ultimate power without the bandwidth or specialities to back it up.
For many companies, this can result in a bottleneck policing structure. If you want to ship, it has to be approved by the design system’s team. It makes designers and engineers using the system feel powerless and the design systems team the “bad guys” — even constraints they have no control over. An example…