Why the payout lands a beat after the action, never during

You tap the final tile and, for a beat, nothing. Then the screen erupts — coins, a chime, a number counting up. The delay is imperceptible if you look for it and unmistakable if it is removed: cut it to zero and the reward feels flat, feels less like something your action caused and more like something the screen just did.

What everyone sees

Instant feedback is assumed to be best — the faster the reward follows the tap, the tighter the loop. Beyond a point that is wrong. A reward delivered at the exact instant of action can read as simultaneous with it rather than caused by it, whereas a reward that follows after a short, clean gap is unambiguously an effect of what you just did, and it is that sense of authorship that the design is protecting.

What is actually happening

Pavlov established that the strength of a learned association depends on the temporal relation between events, with a brief interval in which the signal precedes the outcome supporting the strongest learning. Shanks and Dickinson, studying human judgements of causality, showed that people infer a cause most readily when a short, consistent delay separates action and effect, and that both zero delay and long delays weaken the perceived link. A reward timed a beat after the tap sits in that window: long enough to read as consequence, short enough to read as yours — the interval where action and outcome fuse into a felt cause.

Why it stays hidden

The engineering hides because the gap is below the threshold at which anyone consciously notices timing. Players feel the difference — a satisfying tap versus a dead one — without being able to name that a few dozen milliseconds are responsible. Because the delay is deliberately imperceptible, it is credited to the general “feel” or “juice” of the game rather than recognised as a tuned parameter doing associative work.