Architecture Design for Design Libraries
summary
Comcast teams describe a production-ready Android design system: tokens generated by a Node app and published via GitHub Actions to Android, iOS, web and TV; a Compose-first component library with modifier parameter and nullable slots as required API patterns; templates kept in app layer to avoid business logic leaks; automated docs plus an internal reference app; Material 3 migration that saved thousands of developer-hours; API diffs to catch runtime breaks and a resolver API for CMS/server-driven data.
AI-written summary · about
chapters (13)
- 0:00Welcome
- 1:48Design system basics
- 3:54Benefits of design systems
- 5:03Team-based architecture
- 7:53Architecture building blocks
- 14:08API design principles
- 18:40Composable slots in APIs
- 27:16CMS and server-driven UI
- 28:40Lessons learned
- 33:38Managing API changes
- 35:05Accessibility in components
- 36:31Token automation
- 39:43Q&A
related talks
37mApp Work Ahead! Architecture Design for Design Libraries
18mOne design system to rule them all 1
41mImplementing a Design System in Compose
21mHow We Built the Android Design System for The New York Times
34mDesign System Driven Android Development: A Guide to Automation Tools
37mLet your design evolve, adopt a Design System!
39mAtomic Design in Android
06mLightning talk: Design System - Modular component model