Padding delay with motion is a net loss

What it is

If the result is already painted and the UI still insists on “fly for at least another 300 ms before taps count,” that is not covering a round-trip; it is producing one. Fake delay treats the animation clock as a minimum wait and physically lengthens tap-to-usable. It is not an overrun of a cover: there, a real gap existed at least once; here the gap was written in from the start.

Why it happens

The usual implementation is a delay or “minimum display time”: after ready, still await animation so the transition “looks complete.” The fastest path is then forcibly aligned to the slowest designed duration. The product looks composed in a demo; users pay on every cache hit.

Fake delay is easy to miss because on a slow network it “looks reasonable” — a slow network already waits, so the minimum is hidden under real latency. Only the fast path exposes the tax. Filled duration cannot defend it: there is no gap to fill, and the motion is only hiding a completed state behind a clock.

Where it stops holding

• To prevent a loading indicator from flashing on and off, omit the indicator on very short work; do not pad time so the indicator can appear. Padding is still fake delay.
• Legally or safety-required cooling (undo windows, anti-mis-tap) is not fake delay; those waits have independent consequences. Do not impersonate cooling with a transition, and do not write cooling as a transition.
• A first-run guided demo may be slowed on purpose, but it must be skippable and must not remain on the everyday path.

Applying it

• Forbid “wait for animation end after ready before interaction.” Interactive end state outranks finishing the ease.
• Delete minimum animation durations that exist for completeness. Completeness is a curve-and-distance problem, not a padded clock.
• Check: besides tests on a dead network, measure tap-to-tappable on cache hits. Any fixed floor larger than a frame is a fake-delay candidate.

Related

• Same group: F7.06.1 Motion can occupy a loading gap · F7.06.2 The cover must not outlast the real delay
• Nearby: F7.01.4 Motion that does none of those jobs is pure cost · I2.01.5 A loading indicator on a very short wait creates extra flicker
• Search terms: fake delay · minimum animation duration · time to interactive