Skip to content
Aurelius Black
← Writing

Buying guide

How to choose a UI kit that will not fight you

22 August 2026 · 5 min read

Most UI kits demo beautifully and disappoint on day two. The hero section is gorgeous. The pricing page has a tasteful gradient. Then you open the fourth screen and realise the whole thing is five pages deep.

Here is what to actually check before you pay. All of it learned from kits that looked finished and were not.

1. Does it ship the boring screens?

The home page and the settings page are easy. The screens that decide whether a product feels finished are the ones nobody screenshots. The empty state before there is any data. The list filtered down to nothing. The permission wall. The half-loaded page when one request failed.

A kit that skips these has skipped the hard part, and you will build it yourself anyway. So open the demo and go looking for the empty states. If you cannot find one, that is your answer.

2. Is it one system, or a folder of pages?

There is a real difference between two hundred screens and one design system with two hundred screens in it. In the first, a button on the dashboard is a different button on the settings page, and restyling means a find-and-replace across hundreds of files.

In the second, every screen reads from one set of tokens. A part you learn in one place is the same part everywhere, and you restyle the lot from a single file.

The test is simple. Change the accent colour. If it takes one variable, it is a system. If it takes a search, it is a folder.

3. Does the number on the sales page match reality?

"240+ components" is a claim, and claims drift. Count them. Open the demo, open the file list if it is public, and see whether the number is real or hopeful. A kit that overstates its size will overstate everything else too.

4. Can you leave?

The most important question, and the one nobody asks until they want out. Can you export the source and own it? Is it real code you can read and change, or a locked box? A kit worth buying makes leaving easy, because it does not need to trap you.

5. Does it actually run?

A screenshot proves nothing. A live demo you can click, tab through with a keyboard, and shrink to a phone proves a lot. If the only proof is pictures, assume the pictures are the best it ever looks.

The short version

Buy the kit whose worst screen is good, not the one whose best screen is stunning.

Judge it by the empty states, the token system, the honesty of its numbers, and whether you can walk away with the source. Everything else is the hero section, and the hero section is not the product.

Aurelius Black is twenty interface systems, kits and component packs built as one design system. Every product has a live demo you can click before you pay.