Let your design evolve, adopt a Design System!
summary
Company migrates a decade‑old multi‑platform app to a reusable design system: a shared UI kit (style guide in Figma, components in Sketch/Zeplin earlier), an Android library in a separate repo with a playground app, and a RecyclerView‑based composition model using Lego bricks and a Lego adapter. MVVM code converts business models into testable data‑to‑brick transformers. Rollout takes ~2 years but enables fast RTL, rebrand and dark‑mode launches and aims for ~90% coverage soon.
AI-written summary · about
chapters (10)
- 0:00Introduction to talk
- 0:45Why we needed a design system
- 6:58What is a design system
- 8:25Atomic design explained
- 13:43Our Lego-based approach
- 16:51Android implementation details
- 27:24Challenges and solutions
- 30:12Benefits of the system
- 33:28Summary and key takeaways
- 35:15Q&A session
related talks
20mLet your design evolve, adopt a Design System!
36mConsistency is Key - Working with a Design System
26mHow we engineered our design system
37mConsistency is Key - Working with a Design System
34mDesign System Driven Android Development: A Guide to Automation Tools
18mOne design system to rule them all 1
20mDesign Systems for the Rest of Us
41mImplementing a Design System in Compose
