Publishing practical UI components

21st.dev · Brand Ambassador

21st.dev is a platform where developers find and share UI components. I worked with them as a brand ambassador, and the job was simple to describe: publish components that people would actually want to use.

Simple to describe. Harder to do well.

The bar for a good component

Component platforms fill up quickly with demos that look great in a screenshot and fall apart in a real project. I wanted my components to be the opposite of that.

So each one had to pass the same checks:

• It solves a problem that shows up in real products.
• It reads clearly. Someone can open the code and follow it.
• It handles the unglamorous states: focus, disabled, loading, empty.
• It can be dropped into a project without dragging a pile of dependencies with it.

Clean, useful, practical. If a component was only impressive, and not useful, it didn't get published.

Design and code as one deliverable

Every component was both a design exercise and an engineering one. The visual part had to feel considered: spacing, type, motion, and states that behave the way users expect. The code part had to respect whoever copies it: sensible defaults, readable structure, easy to restyle.

That second part is what makes shared components worth publishing. The moment someone has to fight a component to adapt it, they rewrite it from scratch, and the component has failed at its one job.

What the work represented

Being an ambassador meant my components were also the platform's pitch. Someone landing on 21st.dev for the first time might judge the whole place by one of them. That pressure was useful. It kept the quality bar where it should have been all along.

The work also sharpened something I use everywhere else: the habit of finishing a component completely, not just to the point where it looks done.