For most of the last two decades, digital product design has operated on a simple assumption: friction is failure. Every extra tap, every confirmation dialog, every second between intention and action was treated as a defect to be engineered away. The result was a generation of interfaces built for speed — one-click purchases, autoplay video, infinite scroll, biometric logins that skip the password entirely. Frictionless became shorthand for good design, and good design became shorthand for invisible design.
The Frictionless Decade
The logic behind this orthodoxy was sound, at least in its original context. Early digital products were genuinely difficult to use. Removing unnecessary steps — the extra clicks, the confusing forms, the redundant confirmations — made software more humane. The famous usability maxim "don't make me think" was a reasonable response to interfaces that made people think about the wrong things: navigation, terminology, where a button had gone.
But somewhere between fixing bad design and optimizing for engagement, frictionlessness stopped being about respecting people's time and started being about capturing more of it. The same mechanics that made checkout faster also made it easier to buy something on impulse. The same infinite scroll that removed the friction of clicking "next page" also removed the natural stopping points that once told people when to put a device down.
Where Speed Became a Liability
A handful of product categories have quietly started reversing course. Some communication and email tools now build in a short delay — a window of several seconds after a message is sent — during which the action can still be undone. Certain payment and banking apps insert a deliberate review screen before a large transfer completes, rather than executing it instantly. Screen-time and focus tools go further still, introducing an intentional pause — a loading screen, a short breathing exercise, a single confirming tap — before certain apps will open at all.
None of these are failures of engineering. They are friction added on purpose, by teams that concluded speed was no longer serving the person using the product. A transfer that can't be undone once submitted is not more usable for completing in a single tap; it is simply more permanent, sooner. A feed that never stops loading is not more efficient; it is simply harder to leave.
Deliberate Friction as a Design Pattern
What makes this shift interesting is that it doesn't reject good usability principles — it expands them. Confirmation dialogs, cooling-off periods, and multi-step disclosures are not new ideas. Financial and legal products have used waiting periods and mandatory review steps for decades, long before "friction" was a term in a designer's vocabulary, precisely because some decisions benefit from a pause. What's changed is that this thinking has started moving into everyday consumer software, not just high-stakes financial or legal contexts.
This mirrors an older shift in the history of interface design. When graphical operating systems first added skeuomorphic details — a shutter sound on a camera app, a page-turn animation on an e-reader — the goal wasn't efficiency. It was legibility: giving people a felt sense of what an action meant before flat design decided those cues were unnecessary decoration. Slow interfaces are making a related argument. Some friction isn't decoration or inefficiency. It's information. A pause before a purchase completes tells you, implicitly, that this is a moment worth a second thought.
What Slow Interfaces Ask of Designers
Building friction on purpose is harder than removing it, because it requires a judgment call that pure usability metrics can't make on their own. Reducing steps in a checkout flow is easy to justify with a conversion chart. Adding a pause before a subscription renews, or before a post gets published, has to be justified by a different kind of reasoning — one grounded in what the action actually costs the user if it goes wrong, and how much clarity they had about what they were doing at the moment they agreed to it.
That reasoning tends to ask three questions of any given interaction: How reversible is this action? How well does the person understand what they're agreeing to? And who benefits if this happens faster — the person using the product, or the business behind it? When speed and the user's interest point in the same direction, frictionless design still holds up well. When they diverge, that's usually where a deliberate pause belongs.
A Broader Definition of Usability
None of this amounts to a rejection of simplicity. Most software still benefits from removing unnecessary steps, confusing terminology, and redundant clicks — the original, legitimate targets of frictionless design. The shift is in recognizing that "as fast as possible" was never actually the goal. The goal was always software that respects the person using it, and for some interactions, respect looks like a two-second pause rather than an instant result.
Slow interfaces are not a rejection of good design. They are a more precise version of it — one willing to distinguish between friction that wastes a person's time and friction that protects it.
