What calm design actually means
Calm technology — a term coined by Mark Weiser and John Seely Brown in 1995 — refers to systems that inform without demanding attention.
The idea is simple: the best tools recede into the background. They give you what you need, then get out of the way.
Three principles I apply
1. Defaults should be correct
A calm app does not require configuration to be useful. It ships with sensible defaults that work for 90% of people without touching a setting.
Inbox Zero tools that force you to set up filters before sending your first email fail this test.
2. Interruptions should be opt-in
Notifications are a contract. The app is saying: I think this warrants your attention right now.
Most apps violate this contract constantly. The solution is not turning off notifications — it is apps earning the right to send them.
3. Visual noise has a cost
Every element on screen competes for attention. Borders, shadows, gradients, animations — each has a cost. Calm design spends that budget carefully.
How I apply this to my own work
When designing a UI, I ask: what would this look like if I removed half the elements? Usually the answer is: better.
The hardest design skill is restraint. Anyone can add. Subtracting takes confidence.