← Journal
Quiet software
Loud software announces every click. Quiet software assumes competence and gets out of the way.
In practice that means fewer toast messages, defaults that match real workflows, and copy that explains consequence rather than celebrating features.
We keep a checklist: Can this screen be used without a tutorial? Does empty state teach or scold? Is motion serving orientation or applause?
If three answers are no, we redesign before shipping. Restraint is not austerity — it is respect for the person who opened the app to finish something else.