Information carried by haptics must move to another channel when haptics are off

What it is

Turning haptics off means another channel has to take over that information. Users disable haptics for interference or bodily reasons, not because they no longer need the content. The design must arrange a substitute in advance, or state plainly which information will no longer be pushed.

Why it happens

Once haptics are off, information does not find its own exit; delivery depends entirely on whether the design prepared a substitute. The choice of channel is constrained by information type: binary confirmation can move to a brief visual cue or a sound; source distinction needs a matching visual label; safety alerts need an active channel rather than a record alone. Transfer is not lossless—immediacy and freedom from gaze are haptic advantages—and both are partly lost, so whether to substitute should follow the urgency of the information.

Studying it

Measure delivery after disabling: with haptics off, trigger each event type and record whether users learn of it, the delay, and whether they believe notifications still occur. Variables include event type, substitute channel, and whether disabling was global or graded. Outcomes include arrival rate and trust ratings, the latter showing whether users still believe important information reaches them.

Where it stops holding

When users state that a class of information is not wanted at all, forced substitution becomes harassment and an inspectable record suffices. If no suitable substitute exists, the design should state the consequence rather than dropping events quietly. Substitute channels also overload, so not every haptic can move to the screen.

Applying it

• Define the destination for each mutable haptic class: active delivery elsewhere, record only, or no further delivery.
• Communicate that destination when the user disables it, so the choice rests on known consequences.
• Guarantee at least one active substitute for high-stakes events and verify it under common settings.
• Verification: with haptics off, trigger each event type, check handling against the stated destination, and ask users whether they knew it happened.

Related

• Within the group: D3.12.1 Haptics need a global off switch rather than forced always-on · D3.12.2 Graded control keeps critical haptics while silencing decorative ones
• Adjacent: D2.11.4 Once sound is off, other channels must carry what was muted · D3.09.3 The haptic channel itself has users with perceptual impairments
• Search terms: haptic fallback · channel transfer · mute consequences