Product thinking
The case for calm software
Notifications, badges and streaks all compete for attention. A few principles I use to design products that respect it instead.
Mara EllisonProduct designer & front-end developer · 1 min read
A lot of products are designed to be noticed. Fewer are designed to be put down. I think the second kind is where the most interesting work is right now.
Attention is the budget
Every badge, banner and notification spends a little of someone's attention. When I design a feature, I ask what it costs a person to ignore it, not just what it earns when they tap it.
Three principles I lean on
- Quiet by default. Only interrupt for things a person would be upset to miss.
- Finish the task. A good session ends with a clear sense of being done.
- Be predictable. The same action should always land in the same place.
Calm is not boring
Calm products can still be delightful. The delight just comes from things working the way you hoped, rather than from something flashing for your attention.

