One Button, One Job: Why Interfaces Should Never Make You Wait for an Animation

A UI critique built around a mundane example: tapping the rotate button on a photo. On iPhone, rapid taps are buffered — press the 90-degree rotation eight times fast and each queued rotation fires as the previous animation finishes, landing the image right back where it started. On a Nothing Phone running Android, the button acknowledges each tap with haptics and sound but then silently discards it if a rotation is still animating, breaking the user’s mental model of what they just did.

The author frames this through two lenses. “Situational disability” holds that nearly everyone is temporarily impaired by circumstance at some point, which is why accessibility affects far more people than the small population it’s usually pictured for. The parallel idea, “situational power-user-ness,” argues that even a casual interface like phone photo editing will eventually meet someone using it seriously — say, rotating dozens of landscape document scans — who needs the control to be predictable and fast rather than gated behind decorative motion.

The takeaway is a concrete interaction-design rule: buffering taps is one fix, and interrupting or accelerating the animation on a new tap is another, but under no circumstance should the interface force the user to sit and wait for an animation to complete before it will accept input. A button’s job is to respond, not to make the user watch.