Without progress or haptic cues, a long-press cannot be judged to have taken

What it is

A long-press fires on a point in time while contact is still live. Without progress or a haptic at that point, people cannot tell three things: whether the system is timing, whether the threshold has arrived, and whether lift will already have executed. An unsignalled hold is a door with no latch sound: the only proof is whatever happens afterwards.

Why it happens

A tap can bind a pressed state to the object; a long-press adds a phase change—“this is about to become something else”—that needs its own signal. A ring externalizes remaining wait so someone can abort. A short haptic at threshold pins the phase change to the body even when the pad occludes the target. If the only cue is the result (a menu appearing), people read the pop as system lag and next time press harder or lift earlier. The cue must also reverse: progress should vanish when the finger leaves slop, or people will think the second meaning is already locked.

Studying it

Factor progress on/off against an arrival haptic, with the task “hold until the second meaning appears; abort if it feels wrong.” Dependent measures include successful fire rate, menus that still appear after an abort, and subjective error at the arrival point (felt versus actual fire). Point a high-speed camera at finger and screen to check that progress completes only while the contact is still. A decorative breathing glow that cannot be read as remaining time scores well on “there was feedback” and still wrecks abort accuracy.

Where it stops holding

With sound off, haptics off, or thick gloves, arrival is visual only; if progress is drawn under the pad, it is absent. Push-to-talk and hold-to-record need an “in progress” state, not a bar counting down to a threshold; a long-press progress cue would imply work has not started. Users with photosensitive or vestibular sensitivity may not tolerate pulsed haptics; progress then has to be readable as one discrete beat, not a flicker train.

Applying it

• From down, show a readable approach (ring, fill, a slight lift of the object). At threshold, fire a short haptic or a state jump. Clear both if the finger slides off.
• Do not delay the arrival cue until a menu animation finishes; people need the beat “it fired,” not how pretty the menu is.
• Accept by recording with the finger parked where it occludes the icon, then with audio off: is progress still readable outside the silhouette? Then with picture off, haptics only: can they name which beat was the fire? Fail both and you cannot expect anyone to know whether the hold took.

Related

• Same group: C3.03.1 Long-press trades duration for extra semantics · C3.03.2 Long-press duration thresholds and the perception of waiting · C3.03.4 Long-press semantics are not unified across platforms (select, menu, drag, preview) · C3.03.5 Long-press is a barrier for motor-impaired and older users
• Adjacent: C3.01 Tap · C3.18 Long-press drag to reorder
• Search: hold progress · threshold haptic · press-and-hold feedback