Consistency is Key - Working with a Design System
summary
Deliveroo runs three Android apps and builds a separate UI kit repository published to a private Maven via Artifactory so apps depend on a single source of truth, which reduces rebuilds and improves consistency. A component browser shows every component and its combinations for quick testing. A button component has 42 combinations and uses a deprecation strategy to migrate behavior, components use semantic versioning, and icons are converted to Android vectors and published as a dependency. The setup speeds development but requires ongoing coordination and maintenance.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:04CONSISTENCY IS KEY Working with a design system
- 1:39What is a design system?
- 12:01Creating components
- 24:26Updating components
- 30:57What's next?
- 32:30Design Tokens
related talks
36mConsistency is Key - Working with a Design System
37mLet your design evolve, adopt a Design System!
22mDesign Systems at Deliveroo: Learnings and Frustrations
12mDesign Systems-Revamping Products for Consistent UIs
26mHow we engineered our design system
27m"Design Systems from 0 to 1"
34mDesign System Driven Android Development: A Guide to Automation Tools
40mBest practices for building a consistent design system from design to app implementation