Most software is exhausting. Not because it does too much, but because it talks too much. It pings, it bounces, it pops up, it asks for permission, it reminds, it confirms, it celebrates, it nudges. Every product wants a little of your attention, and there are now thousands of products in the room.
We have been thinking about this as a design problem. What does it take to build software that does its job and then is quiet? Below is a working list — opinionated, incomplete, written down so we can argue with it later.
Notifications are a tax
Every notification a product sends withdraws a small amount from the user's attention. Most products treat that attention as a free resource. It is not. It compounds. By the end of a working day, a user has paid attention tax to twenty different apps, and the cost is cognitive fatigue.
Our default rule is: no notification unless the user explicitly opted in to that specific notification. Not a global "send me email" toggle — a checkbox next to the actual thing. If a user does not see the value clearly enough to opt in, the value was not there.
On JuuLinkAI we send exactly two emails: a welcome email when you sign up, and a receipt when you upgrade. That is it. No weekly digests, no "you have not logged in for a week" nudges, no feature announcements. If we build something worth announcing, we put it inside the product, where the user will see it the next time they need the product anyway.
Animations should be useful, not entertaining
A bouncing transition is fun the first time. The hundredth time, it is friction. We use motion sparingly and almost always for one reason: to show the user how one state became another. A drawer slides in from the right because the right is where it lives. A card moves to the top of a list because it was just edited. The motion is doing work — explaining a change — not performing.
We avoid loading spinners wherever possible. A spinner is a confession that the system is going to make the user wait without giving them anything to look at. Where we cannot avoid waiting, we use skeleton states that hint at the shape of what is coming. Where we can avoid waiting, we use optimistic UI — assume the action succeeded, show the result immediately, reconcile silently if it failed.
Confirmations are mostly an admission of bad design
"Are you sure you want to delete this?" — almost always a sign that the system has no undo. Confirmations are not safety. Undo is safety. Confirmations are the system asking the user to do its memory work for it.
Our rule: if an action is reversible within thirty seconds, we execute immediately and show a small undo toast for ten seconds. If an action is genuinely destructive — deleting an account, cancelling a subscription — we use a confirm dialog, but only that one time. Not for deleting a row. Not for closing a tab.
Confirm dialogs are the software equivalent of being asked "are you sure?" by a friend after you ordered. They are not safety. They are anxiety.
Defaults are the loudest part of the product
Every default is an opinion. The default email frequency, the default privacy setting, the default sort order, the default font size — each of them shapes how the user experiences the product before they have clicked anything. Most teams under-invest in defaults because they feel like a thing the user can change. In practice, almost no one changes them.
We spend a disproportionate amount of design time on defaults. We argue about whether new notifications should be on or off. We argue about whether dark mode should follow the system or default to light. We argue about whether the search bar starts focused or not. These are not small decisions. They are the product, for almost everyone.
Onboarding is the wrong shape
Most onboarding flows are a sequence of full-screen modals that teach the user the product before they have used it. This is backwards. Nobody remembers an explanation they did not yet need.
We prefer onboarding that lives inside the product, attached to the actions a user is already taking. The first time a user clicks Generate, a small tooltip explains what is happening. The second time, no tooltip. We assume the user learns by doing, because that is what people actually do.
We also avoid checklists. The "getting started" sidebar with five items to complete is a productivity-app cliché. It turns the user's relationship with the product into homework. We would rather they discover features the same way they discover features in any well-designed object — by needing them.
Settings are a graveyard
Every time a team cannot decide between two options, they add a toggle. Settings pages are where these unmade decisions go to die. The cost is borne by the user, who now has to read forty descriptions to find the one that affects them.
Our rule of thumb: a setting must save at least 20% of users at least 20% of the time, or it should be a default. If we cannot make the case, we remove the setting. JuuLinkAI's settings page is one screen long, and we are proud of that.
Copy is interface
The words in a product carry as much design weight as the layout. A button labelled Submit is a button that does not respect the user's time. A button labelled Publish profile tells you what is about to happen. We rewrite every label at least once before launch, often more.
Quiet software tends to use shorter words, plainer sentences, and fewer exclamation marks than the average SaaS product. There is no rule about this. It is a habit. The habit comes from reading the product out loud, in a calm voice, and asking whether anyone speaks this way at home.
The compounding effect
None of these decisions, individually, are dramatic. Each saves a user maybe a quarter of a second, maybe a small spike of mild irritation. The case for quiet software is the case for compounding — that small considerations, repeated across every interaction, add up to something that feels different.
The phrase we keep coming back to is from a Japanese tea ceremony manual we read once and only half understood: let the guest feel that nothing happened. That is the design target. Not delight. Not engagement. Not stickiness. Just — nothing happened, I got what I came for, and I am leaving lighter than I arrived.