~/blog/notes-on-building-calm-interfaces← Back to all notes

Notes on building calm interfaces

Small decisions that add up to a more focused, human user experience.

5 min read#design#ux

A calm interface is not an empty interface. It is one that spends attention deliberately, keeps its promises, and gives every visual signal a job.

Reduce competing signals

When everything asks to be noticed, the user has to rebuild the hierarchy themselves. Start by choosing one primary action, one reading order, and a small vocabulary of states.

  • Use contrast to explain hierarchy, not to decorate it.
  • Reserve motion for change that benefits from continuity.
  • Let spacing group related ideas before adding containers.
Calm is the result of clear priorities, not the absence of personality.

Design the recovery path

The character of an interface is clearest when something goes wrong. Useful errors preserve context, explain what happened, and offer one credible next step.

No command output