The case for slower interfaces
1 min read
We have spent a decade shaving milliseconds, and mostly that was right. Nobody misses spinners. But speed and clarity are not the same thing, and sometimes a short, honest transition explains a change better than an instant swap.
Where instant goes wrong
When a list reorders instantly, your eye loses the item you were looking at. When a panel appears without motion, it is hard to tell where it came from or how to put it back. The interface is fast, but you are slower — you have to rebuild your mental map every time.
Motion is not decoration. It is the interface explaining what just happened.
A small budget
I give most transitions a budget between 150 and 250 milliseconds, and I spend it on continuity rather than flourish: things move from where they were to where they are going.
.panel {
transition:
transform 220ms cubic-bezier(0.22, 1, 0.36, 1),
opacity 160ms ease-out;
}
@media (prefers-reduced-motion: reduce) {
.panel {
transition: opacity 120ms linear;
}
}
Two details matter more than the numbers. First, the curve: a strong ease-out makes motion feel responsive because most of the movement happens immediately. Second, the fallback: people who ask for reduced motion should still get a soft fade, not a hard cut.
When to be fast anyway
Keyboard actions, frequent toggles and anything triggered dozens of times an hour should be instant or close to it. The rule I use: the more often something happens, the less it should move.
Slow, here, never means sluggish. It means taking just enough time to be understood.