Atomic design methodology


I first came across the atomic design methodology around 2 years ago while doing research for a branding project. It basically involves breaking down user interfaces into smaller, reusable components, allowing for more systematic design and development processes.

You start by creating atoms and work your way up, forming molecules, organisms, and finally templates and pages.

I’ve since realized its broader applicability in web development for creating reusable components. 🔄

Just like in the atomic design methodology, in front-end development, components are also created and organized into a system based on their level of complexity and reusability.

Breaking down larger elements into smaller, more manageable parts makes sense because it creates consistency, scalability, and maintainability in both design systems and codebases.

It can be tedious at first to get used to and to implement, and some might not bother with smaller-scale projects, but in my humble opinion, the time it takes to set up is usually less than the time it will save you. Plus, it will make the project look more professional because it will be consistent and coherent. 🌟

These are some of the thoughts that occurred to me while I was creating this design system for a camping app. ⛺

Do you see the utility of this approach? I would like to hear your thoughts on it 🙂

Content table 

Hola, I’m Inés, a web developer with a background in product management and design. I offer practical and tailored solutions.

Share if you liked it