App Work Ahead! Architecture Design for Design Libraries
summary
A design library evolved over 5 years from XML to Compose, layering on Material and automating tokens for Android, web and iOS; it delivers explicit, ergonomically named APIs with default objects and slotted helpers so engineers and CMS content map cleanly to components, improving release speed and accessibility. CI uses Gradle API dump to detect ABI changes, publishes via GitHub Actions and keeps deps in sync with a renovate bot. The result: fewer one‑off widgets and faster, auditable platform updates.
AI-written summary · about
chapters (9)
- 0:00Design systems overview
- 3:55User needs in design systems
- 7:04Architecture principles
- 13:33API design requirements
- 17:53API guiding principles
- 20:05Button API case study
- 25:02Slotted vs explicit APIs
- 29:42API design best practices
- 31:30Q&A
related talks
40mArchitecture Design for Design Libraries
36mBuilding UI Consistent Android Apps
37mConsistency is Key - Working with a Design System
25mFrom Design Systems to Component Libraries
26mHow we engineered our design system
21mA Common Design Language Let Designers and Developers talk to each other
37mLet your design evolve, adopt a Design System!
34mDesign System Driven Android Development: A Guide to Automation Tools