Atomic Design Theory in Practice
summary
Argues that an atomic design system — with atoms molecules organisms templates pages — prevents duplicated UI, speeds prototyping, and removes constant pixel-nudging by enforcing a style guide and reusable components. Shows concrete Android code: custom view XML + inflate, parse styled attributes, findViewById wiring, and adding click listeners; mentions declarative options like Jetpack Compose (pre-alpha) and SwiftUI (beta) and tooling like Anko and a Fractal iOS library. Requires designers, developers, and product alignment, a minimal API surface, and iterative rollout rather than perfection.
AI-written summary · about
chapters (7)
- 0:00Introduction to standardization
- 3:57What is atomic design theory
- 7:01Style guide as blueprint
- 13:28Building components in code
- 25:01Why use atomic design
- 27:09Team roles and coordination
- 30:23Challenges and next steps
related talks
39mAtomic Design in Android
24mAtomic Design : A recipe for success
40mAtomic Design Software Architecture Illustrated with Angular 2
30mAtomic Design: Breaking Up is Hard to Do
28mBetween Design and Implementation in Atomic Design
37mIs Atomic Design Dead?
44mAtomic Design and Storybook to Boost Frontend Dev Productivity
26mHow we engineered our design system