The pressed state confirms that contact was recognized
Aliases: active state · touch-down feedback · press feedback · contact acknowledgement
What it is
A pressed state, often called an active state, is transient feedback while a finger, mouse, or other pointer is down and remains in contact. It confirms “contact was recognized,” not “the command completed.” A depressed button, darker fill, surface-scale change, or light haptic pulse can express pressing; triggering, cancellation, and later processing belong to subsequent states. Conflating contact confirmation with an outcome leaves people unable to interpret holding, dragging out to cancel, or waiting for an asynchronous result.
Why it happens
Touchscreens have no mechanical travel from which people can reliably infer reception. A pressed state maps a contact event to a near-immediate visible change, creates continuous control, and gives a chance to check the target before release. With no change, a light tap and a miss are indistinguishable. If it arrives only on release or network response, evidence of contact is severed. Mouse interaction also benefits, particularly where press, drag, and cancellation differ.
Studying it
Vary target size, finger posture, animation latency, and cancellation gestures, comparing miss perception, repeated taps, drag-out cancellation success, and perceived control with and without a pressed state. Record pointer or finger trajectory with interface frames to see whether feedback appears during contact, follows the object, and becomes occluded. Eventual successful activation is insufficient: users may succeed through retries while lacking confirmation at every press.
Where it stops holding
A pressed state must not imply that an irreversible submission already occurred. Release-to-activate controls need a legible cancellation interval, while immediate-trigger controls cannot use it to conceal real consequence or delay. Hardware keys, voice commands, and automation calls may have no sustained-contact phase and should not simulate one. Excessive scale or displacement can destabilize the target and sacrifice text legibility.
Applying it
- Specify down, hold, exit, release, and cancellation states for direct manipulation, with feedback appearing as soon as contact is recognized.
- Retain the style only while the contact remains valid; when a finger exits a cancellable region, show the change rather than executing silently.
- Keep pressed styling distinct from completion, loading, and error; one color should not carry the entire state sequence.
- Observe one-handed thumb use, edge targets, and rapid repeated taps. “I don’t know whether it registered” and retapping are evidence of failed contact acknowledgement.