About Design tools

Design tools have split into two jobs that used to be one. There are tools for deciding what to build — wireframes, prototypes, user flows — and tools for producing the artefact, whether that is a component library, an icon set, or production markup. Founders shopping in this category usually need less of the first than they think and more of the second.

The listings here cover prototyping and design systems, UI kits and component libraries, illustration and asset tools, brand and identity products, and the growing set of tools that turn a design into code without a handoff meeting.

The judgement call is where your bottleneck actually is. If you cannot decide what the screen should do, no component library helps. If you know exactly what it should do and it takes three days to build, a design system will pay for itself in a fortnight. Solo founders in particular tend to over-invest in exploration tooling and under-invest in anything that shortens the distance between a decision and a shipped screen.

What to look for

Handoff, or no handoff

Tools that produce code you would actually keep are worth more to a small team than tools that produce beautiful specs for a developer who does not exist. Check what comes out the far end.

Licensing on assets

Icon sets, illustrations, and templates carry licences that differ on commercial use, redistribution, and whether attribution is required. Read it once now rather than during a rebrand.

File portability

Design files outlive subscriptions. Open or widely supported formats mean a price change does not strand three years of work behind a paywall.

Does it match your stack

A component library built for a framework you do not use is a reference, not a shortcut. The saving comes from dropping components in, not from translating them.

Design questions

Keep reading