Designers and Developers, Let’s Create the Difference!
summary
How to make projects stand out when teams rely on component libraries like Material or Bootstrap. The talk explains methods for defining a product identity, then building functional UI elements into a coherent Design System using Atomic Design, with practical developer best practices for reusable, brand-consistent systems.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:07Similar site problem
- 3:11Adding a designer isn't enough
- 5:18Co-building with wireframes
- 7:04Graphic research and mood board
- 8:28Creating a design system together
- 11:16Design atoms and grid
- 13:02Component molecules and organisms
- 14:05Storybook for design system
- 16:55Living and scalable system
- 18:02Code implementation
- 20:29Final app result
- 21:57Recommended tools and costs
- 22:39When to set up a design system
- 23:42Design system group vs project
- 24:45Why differentiate
- 25:30Q&A
related talks
45mDesigners, developers, let's make a difference…
34mDesigners, Developers, Let’s Create the Difference!
25mHow to understand the perspectives in Product Design processes as a developer
25mPanel discussion about design systems
35mDesign system - From a Developer Point-of-View
15mHoly War between Designers & Developers
12mDesign Systems-Revamping Products for Consistent UIs
21mDesign Systems 101: The Developer Approach to Better Frontends