The products we love rarely shout. They don't fight for attention with badges, banners and blinking dots. They get out of the way so we can do what we came to do. That quality — calm — is designed, not accidental.
Calm starts with fewer decisions
Every option on a screen is a small question the user has to answer. Before adding a setting, a toggle or a second button, ask whether the product could simply make the right choice instead.
- Pick sensible defaults and let people change them later.
- Group rarely-used options behind a single, clearly-labelled entry point.
- Remove anything that exists "just in case".
Hierarchy does the talking
When everything is bold, nothing is. A calm interface has one obvious primary action per view, supported by quieter secondary ones. Size, weight and colour should all agree on what matters most.
Use colour like punctuation
Reserve your accent colour for the things that need it: the primary action, the current selection, an important status. Used sparingly, colour guides the eye; used everywhere, it becomes noise.
Motion with a purpose
Animation should explain, not decorate. A panel that slides in from the button that opened it tells people where it came from. A spinner that appears after a 100ms delay avoids a flash on fast connections. Anything people see dozens of times a day should be fast — or not animate at all.
Five habits worth keeping
- Design the empty state first.
- Write the interface copy before the layout.
- Test with real content, never lorem ipsum.
- Remove one element from every screen before shipping.
- Use the product yourself for a week.
Calm isn't the absence of features. It's the absence of friction.
Designing for calm is a practice, not a style. The more you do it, the more you notice how loud most software is — and how good it feels when it isn't.
Enjoyed this? Let's talk.
Talk to me