On quiet software

Some software is loud. It greets you, celebrates you, asks how it's doing. Other software just works and gets out of the way. I prefer the second kind, and I'm trying to build more of it.

What quiet looks like

Quiet software has a few things in common:

  • It remembers what you were doing.
  • It doesn't move things around between visits.
  • It uses motion to explain, never to impress.
  • It's fast enough that you never think about speed.

None of these show up well in a screenshot. That's sort of the point.

A test

When I'm unsure whether something belongs, I ask whether I'd notice if it were gone. If I wouldn't, it probably shouldn't be there.

The design is successful when every element feels necessary.

That sentence has been taped above my desk for a while. It's harder to follow than it sounds.