Creating DoorDash’s native mobile design system
summary
DoorDash’s Prism system claims a single native library powers three product surfaces and now contains 38 native mobile components after a multi‑year build that began in 2017 and serves 65 product designers and 350 engineers. Process artifacts include a Figma design Direction doc, Google Sheets “component ingredients,” component spec sheets, Figma APIs plus Style Dictionary for token codegen, and outputs of iOS UI/asset catalogs (UIKit and SwiftUI) and Android Kotlin Compose and XML. Several components needed custom builds; a slider and timeline reveal what breaks when design direction is skipped.
AI-written summary · about
chapters (11)
- 0:00DoorDash design system intro
- 2:57Design system challenges
- 3:40Three-phase design process
- 4:42Design Direction phase
- 6:26Past design mistakes
- 7:08Detail design phase
- 9:59Handoff process and Figma
- 11:43Code generation for mobile
- 14:34Cross-platform components
- 17:48Ship review and adoption
- 19:56Recap and takeaways
related talks
22mDesign Systems at Deliveroo: Learnings and Frustrations
20mDesign Systems for the Rest of Us
26mDesign Systems of a Down: Steal this Guide!
09mDesign Systems Showcase: TACKling Our Design System
37mConsistency is Key - Working with a Design System
33mHow to Build a Universal Design System
20mBuilding a Mobile Design System
26mHow we engineered our design system