Overlong debounce blocks intentional rapid taps

What it is

People sometimes mean to tap the same target as fast as they can: fire, rhythm, skip dialogue, hold a counter down. If the debounce interval is longer than the repeat period those hands can stably produce, the second and later intended taps are dropped. Fire rate caps, the counter skips, “I pressed and it didn’t come out.” That is not bounce being suppressed. Legal high-rate repeats are being treated as artifacts.

Why it happens

Intended-repeat period is limited by muscle, haptic confirmation, and visual confirmation. Skilled players can sit closer to the bounce peak than novices, but usually still wider than bounce. A globally applied, pay-button-right latch also cuts game fire, space-to-skip, and plus-mashing. Worse, if the latch resets on dropped taps, each discarded hit pushes the timer out, so the more someone mashes the farther the next legal fire—urgency dulls the control. If haptics play only when a tap clears the latch, players use vibration as confirmation, miss it on dropped taps, and mash more, colliding with the latch again. Writing the interval as “the length of one animation” yokes repeat rate to animation, independent of input skill.

Studying it

Take tasks people mash (shooting, increment, skip), measure skilled interval distributions, and overlay the current latch. Independent variables are interval length, whether the latch resets on dropped taps, and haptics. Dependent measures are effective fire/increment rate over finger motion rate, count of dropped intended taps, and ratings of “dull, ate my input.” Split novices and skilled players: skilled distributions sit closer to bounce, so the same latch hurts more. Do not set a game interval from pay-button participants.

Where it stops holding

Some accessibility users cannot produce short-interval taps; a game whose only fire is mashing is not saved by a shorter latch—they need hold-to-repeat or aim assist. Autofire (hold to repeat) has its own clock and must be specified not to die under the tap latch. A double-tap recognizer’s window also eats the second tap; that is gesture disambiguation, not overlong debounce, and should be scored separately. A Web double-click-to-select sitting on a game canvas adds the browser’s own gap.

Applying it

• Give game fire, increment, and skip a short latch just to the right of the bounce peak, or a dedicated hold-to-repeat clock; do not reuse pay debounce.
• Make dropped intended taps visible on an input debug HUD, and tune by effective fire rate rather than by whether bounce complaints vanished.
• Offer hold-to-repeat or long-press charge for people who cannot mash, so a skilled short interval is not the only legal input.

Related

• Same group: C2.22.1 Bounce clicks are rapid extra triggers from contact rebound, not intent · C2.22.2 Repeat-trigger intervals trade responsiveness against debounce · C2.22.4 Mechanical key bounce likewise requires software debounce
• Nearby: C3.02 Double tap · C3.19 Gesture conflicts and disambiguation
• Search terms: rapid tap · fire rate · debounce