Research-driven design systems
summary
An internal research report interviews 17 designers and engineers and surfaces concrete failures: duplicated Confluence pages, separate Figma theme libraries, missing Android components, and long onboarding. The team builds a single foundations library in Figma, migrates components, tests the fixes by bootstrapping an Android library that uses a gallery app and designer goggles for in‑app inspect, and reports faster handoff, clearer naming, fewer duplicates and measurable onboarding time saved.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:32Identifying the problems
- 3:53Research approach
- 6:12Key research insights
- 8:59Deep dive into challenges
- 12:14Feedback and opportunities
- 14:27Quick wins and immediate changes
- 17:11Android implementation
- 19:23Long-term strategy
related talks
18mMaking the Things That Help Others Do Their Thing
14mRethinking Designer-Developer Collaboration
18mDesign Systems in Practice
26mCrafting Cohesion A Design System Journey Without a Dedicated Team
36mConsistency is Key - Working with a Design System
40mBest practices for building a consistent design system from design to app implementation
34mDesigners, Developers, Let’s Create the Difference!
24mDesign from the realm of open-source