The design of quiet software.
How we think about an interface for someone who is already carrying a lot. The short answer: the screen should ask for less than it gives back.
Most software we admire is loud about its features. The icon set is rich. The dashboard is dense. The notification stream is constant. That works for software that lives in your work day, where the screen is the job.
Pivotical lives in a person's life, not their job. The interface has to be quiet. It has to ask for less than it gives back. It has to know the difference between a thing you need to see now and a thing that can wait until you choose to look.
Three rules we keep
- 01If a card is on screen, it is there because a human, your future self included, decided it should be.
- 02If a number is shown, the unit and the trend are shown with it. Numbers without context are noise.
- 03If a colour signals concern, it earns the right to. We use red rarely, and we never use it for emphasis.
Quiet doesn't mean empty. It means the page knows what it's for and doesn't try to do anything else.
Ask the assistant
The Pivotical assistant has read this article and the rest of the site. Press ⌘K and ask it anything.