How to understand the perspectives in Product Design processes as a developer
summary
Explains how design systems become reusable product infrastructure: built Sketch component libraries reused across multiple e-commerce and aviation projects, following atomic design and the Material 2014–2016 rollout; maintenance proves hardest because changing existing components breaks features, so teams enforce naming, folder structure, and documentation. Claims a design system is a living organism that improves with usage data and feedback, and asks designers to provide problems not prescriptive solutions so developers can implement consistent, simple code.
AI-written summary · about
chapters (8)
- 0:00Introduction and thanks
- 0:45What is design and design systems
- 3:54Definition and purpose of design systems
- 7:29Building vs using existing design systems
- 12:11Core components of a design system
- 17:35Maintaining and evolving design systems
- 22:57Developer-designer collaboration tips
- 24:08Q&A and closing remarks
related talks
56mDesign System as a Product
23mDesign Systems 101
35mDesign system - From a Developer Point-of-View
38mDesign Systems Mastery: From Patterns & Principles to Product Excellence
46mBuilding & Managing Design Systems
25mPanel discussion about design systems
27mFoundations of Design Systems
34mDesigners and Developers, Let’s Create the Difference!