Earlier this year, Jeremy Dizon led the project to enhance the Lyft Product Language (LPL) Native component library. In this blog post, he talks about the strategy they’ve used, the reason behind incorporating lightweight user research, and some key learnings from this 6‑month long project. Sometimes creating a new version of each component is the right approach, and major updates to Figma features provide a good opportunity for this work.
Jeremy Dizon, Runi Goswami, Michael Yom, and Joanne Deng from Lyft. “Like any product, a design system is only as useful as it is usable. In this session, the Lyft Design Systems team will share the end-to-end resources that enable their system users to build consistent, quality products and features at scale. We’ll learn about their most resilient processes, their past mistakes, their new-ish contribution model, and more.”
“Design systems sit at the intersection of design and development. Lyft teammates Jeremy Dizon, Design Systems Product Designer, and Alex Lockwood, Design Systems Staff Engineer, will show off their design system and share how they collaborated to build it.”
we released an internal @figmadesign plugin today at @lyftdesignteam that allows designers to seamlessly switch between light and dark mode directly within Figma. and yes, it does support elevation overlays. pic.twitter.com/z7TLp0xpXX
— Alex Lockwood (@alexjlockwood) July 29, 2020
Alex Lockwood from Lyft shares a few examples of how their team used Scripter plugin to build a design system library and automate tasks that would have otherwise taken hours or days to complete.