calm is part of the interface

software should make the next step easier to see

i want software to feel calm, especially when the work behind it is complicated.

calm does not mean empty or slow. it means the interface tells me what is happening, what needs my attention, and what will happen if i act. a useful error gives me a next step. a useful loading state tells me whether to wait. a useful empty state tells me how to begin.

when a product leaves those questions unanswered, the user has to supply the missing design themselves. i do not want people to spend their attention guessing at my system.

clarity is a feature. so is helping someone feel in control.

← back to writing