Skip to content

//Design

The interface should tell you the truth before you tap

5 min read

Restraint, hierarchy and whitespace get most of the attention in design writing. They matter. But the interfaces people actually trust are the ones that are honest about state, early, before anyone has invested effort.

Failure should be visible before the tap

On a booking app we built, the slot grid greys out times that are already taken. Nothing about that is clever. The alternative is what most booking flows do: let you tap an unavailable slot, then explain the problem afterwards.

The difference is where the user finds out. One version tells you the truth while you are still deciding. The other lets you commit, then takes it back. Same information, and only one of them feels like the product is on your side.

The same instinct applies to a five-minute hold on a slot during checkout. Showing that the hold exists, and that it expires, is not clutter. It is the difference between a user who understands why the slot disappeared and a user who thinks the app is broken.

Hierarchy is a series of refusals

Clarity comes from hierarchy, and hierarchy comes from deciding what does not matter. If everything on a screen competes for attention, nothing wins. Pick the one thing that matters most and let the rest recede.

This is harder than it sounds, because every element on a screen has someone who wants it there. The useful question is not “is this useful?” — almost everything is, a little. It is “if a person only sees one thing here, should it be this?”

Whitespace is not wasted space

Dense information becomes legible through spacing more than through typography. Grouping, breathing room, and consistent rhythm do more for comprehension than another weight of the same typeface.

The test we use: can someone scan the screen and find the one thing they came for without reading it? If they have to read to navigate, the layout is doing too little work.

Every element should earn its place

If a thing on screen does not help someone decide or act, it is a candidate for removal. Not a certainty — some things are there for reassurance, and reassurance is a job. But it should have to justify itself.

We have never removed something and later wished it back nearly as often as we have added something and wished it gone.

The version people trust

Good interface design is mostly the discipline of showing state accurately: what is available, what is happening now, what will happen if you continue, and what went wrong if it did.

Get that right and the aesthetics have something to sit on. Get it wrong and no amount of polish will make the product feel reliable, because it is not behaving reliably. It is just behaving attractively.