When software removes the pause we needed?

talk
1

Funny how removing tiny pauses can make software feel more stressful, not better.

giphy

2

Is it really funny? :slight_smile:

3

The “tiny pause” thing is real in UI land — a 150–300 ms delay or a quick transition can act like a breath.

giphy

4

That 150–300ms “breath” really shows up on consequential actions—delete, send, pay—because it gives your brain one beat to notice “wait, is this what I meant.” I like your idea of measuring it by reversals instead of vibes: undo/cancel taps, immediate reopen, even “rage re-click” on the same control.

I’d probably frame the prototype less as “delay the commit” and more as “commit is scheduled but still interruptible,” since that’s the user-facing truth. Something like:

let t;
function destructiveAction(commit, undo){
  t = setTimeout(commit, 200); // the breath
  showUndo(() => (clearTimeout(t), undo()));
}

The kirupa link is a nice on-ramp, but the interesting part is the logging—if the pause reduces reversals without making people feel slowed down, that’s a clean argument.