Notes on building calm software
The best tools feel like a quiet room. Some scattered notes on what makes software calm, and why so little of it is.
Calm is not a feature you can add at the end. It’s the accumulated absence of a hundred small demands — badges, banners, nudges, spinners, notifications that could have been a log line. You notice calm software the way you notice a quiet room: not by what’s there, but by what isn’t pressing on you.
Some notes, in no particular order.
Calm software finishes its sentences. When an operation completes, it says so once, plainly, and gets out of the way. It doesn’t celebrate. Confetti after a saved file is a tax on every future save.
Calm software has a resting state. There is some screen where nothing is blinking, nothing is fetching, and nothing wants anything from you. If every state of the app is trying to convert you to some other state, the app has no floor to stand on.
Calm software respects the difference between urgent and new. Almost nothing that happens inside a computer is urgent. Interfaces that treat every event as an interruption train users to ignore everything — which eventually includes the one thing that mattered.
Calm software is slow to speak in color. If the UI is mostly quiet grays, a single red word carries enormous weight. Spend saturation like money.
The strange thing is that calm is cheaper to build. Fewer states, fewer animations, fewer systems fighting for the same corner of the screen. What’s expensive is the restraint — every team has someone arguing that their feature deserves a badge, and the badge is always individually reasonable.
The whole game is remembering that attention is the user’s, not yours. You’re borrowing it. Calm software is what it looks like when the loan is repaid on time.