Bulletproof development with design systems
summary
Claims that a design system stops inventory and duplication problems and makes releases safer while improving accessibility and onboarding, and shows which tools and practices enable that: Sketch and Zeplin plus Abstract for design versioning, Framer X and react‑sketch‑app for prototypes, Storybook with visual regression and snapshot tests for CI, and component‑driven development with strict code review and semantic versioning. Migration follows step‑by‑step migration, not big‑bang, and the outcome is a measurable drop in rework and faster, more consistent releases.
AI-written summary · about
chapters (12)
- 0:00Start
- 17:50Source of Truth Hell
- 19:00Design Hell
- 19:52Inventory Hell
- 20:31Feature Duplication Hell
- 21:18Performance Hell
- 22:10Architecture Hell
- 23:01Onboarding Hell
- 24:36Popup/Alert Hell
- 25:21Release Day Hell
- 33:08Feedback Session Feedback Session
- 43:28Ds version 2
related talks
18mDesign Systems in Practice
46mBuilding & Managing Design Systems
35mDesign system - From a Developer Point-of-View
34mDesigners, Developers, Let’s Create the Difference!
25mBuilding a Design System as a team
25mSecrets to a Successful Design System
50mManaging Design Systems, from Features to Roadmaps
20mDesign Systems for the Rest of Us