Advanced Design System Considerations
summary
A five‑person design system team at Stripe supports ~2,000 engineers and designers, so the talk argues for minimizing cross‑component coupling with shared tokens that let button and icon size rules override locally, shows an accessible color system already in use, and demos a prototype modifier‑based rendering approach (SwiftUI‑inspired) that can emit React Svelte or design‑tool outputs. The claim is that decentralizing configuration and shipping small atomic components reduces complexity; prototypes work but remain partly experimental.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:43stripe
- 12:32Customize /Button
- 16:04create relationships without encoding strict dependencies
- 25:48what does success look like?
- 26:31decentralization & inversion of control
- 26:52design systems are about values
related talks
20mDesign Systems for the Rest of Us
46mBuilding & Managing Design Systems
25mBuilding a Design System as a team
25mPanel discussion about design systems
35mDesign system - From a Developer Point-of-View
18mDesign Systems in Practice
13mDesign systems and how to use it
24mTiny Design Systems for Tiny Teams