Let’s talk

Back to writing

Design Systems

How I’d take Atomic Design from Figma into React

A design system starts to earn its keep when reusable components survive real data, real rules, and real errors.

It’s tempting to open a fresh React project and build a library of buttons, inputs, and cards before building a page. I prefer to pick one real flow first. A booking form gives me plenty to work with: a date, a package, traveller counts, a price, and a button that has to do something useful.

Brad Frost’s Atomic Design gives me a vocabulary for describing how those pieces fit together. A button or input can be a small building block. The traveller counter combines smaller parts. The booking panel brings them together, and the actual tour page shows how well the whole thing copes with real content.

Work out who owns the state

React’s Thinking in React encourages you to identify the smallest amount of changing data you need. If the total is fully determined by the package and traveller count, I’ll calculate it from those choices. If the server is responsible for pricing, I’ll show its result and handle the wait or error. Keeping two independently editable versions of the total is an easy way for a page to tell the customer two different things.

Share the parts that really repeat

A package picker and a subscription picker can use the same field styles while following different rules. I’d share the field and put each feature’s pricing and validation where it belongs. Before pulling a whole component into the shared library, I’d try it in another real flow and see what carries over. The answer is often smaller and easier to maintain than the component I was about to build.

Have something in mind?

Let’s talk.

Tell me what you’re building. Let’s find the right way to bring it to life.