Designing for restraint: the case for boring interfaces

There's a temptation, on every project, to make the interface interesting — to add the unexpected interaction, the clever transition, the layout nobody's seen before. Most of the time, that temptation is worth resisting.

Novelty is a tax

Every novel pattern is something the user has to learn. A custom dropdown, a reinvented scroll, a menu that opens sideways — each one asks for a few seconds of attention the user didn't plan to spend. Spend that budget on the things that are genuinely yours, and pay the familiar price everywhere else.

Conventions are accessibility

Standard components carry decades of accumulated care: keyboard support, screen-reader semantics, focus handling, reduced-motion behavior. The moment you rebuild a native control from scratch, you inherit the job of reimplementing all of it — and most reinventions quietly skip the parts you can't see.

Restraint, here, isn't laziness. It's choosing not to reintroduce solved problems.

Where restraint ends

None of this is an argument for blandness. The place to be bold is the part of the product that is uniquely yours — the hero moment, the signature motion, the one screen people screenshot and send to a friend. Be ruthless about spending your novelty budget there, and almost nowhere else.

A checklist we actually use

Before we ship a non-standard pattern, we ask three questions:

1. Does this solve a real problem the standard pattern can't?
2. Will it still work with a keyboard, a screen reader, and reduced motion turned on?
3. Is this the screen we want people to remember — or just one we got bored building?

The best interface is the one the user never has to think about. Save the fireworks for the one moment that earns them.