Cosmos: How to create a better scalable UI
summary
Cosmos standardises Android UI across a 60‑engineer mobile org and 20+ designers by shipping an atomic library of 70+ components, immutable component models, a component controller that dynamically swaps compatible views, and an MVI + model-watcher pattern that only updates changed fields. It adds a gallery-driven visual regression pipeline using Facebook screenshot-test library and per‑brand theming from centrally stored tokens + Gradle plugin (Sketch → vector drawables → linked colors), cutting redesign work to a single config update.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 5:10Problems with legacy UI
- 10:11Improving UI tooling
- 16:00Component reuse challenges
- 19:58Visual regression testing
- 23:17Design tokens and assets
- 29:48Solving consistency issues
- 30:30Scaling across apps
- 34:11Processes and team sync
- 36:45Q&A
related talks
26mHow we engineered our design system
36mBuilding UI Consistent Android Apps
36mConsistency is Key - Working with a Design System
39mRe-Compose your UI: building an atomic design library
32mUI Development Made Simple
21mHow We Built the Android Design System for The New York Times
40mArchitecture Design for Design Libraries
34mDesign System Driven Android Development: A Guide to Automation Tools