Silent mode is expected to hand notification duty to haptics

What it is

In silent mode, users expect haptics to fill the place sound vacated. Enabling silent means "make no noise, but still let me know," which makes touch the default receiving channel. If silent mode also yields no haptic, users find they neither hear nor feel anything and notifications fail entirely.

Why it happens

The expectation follows from how users read the word "silent": it removes sound, not the notification. A system implementing silence as "notification intensity to zero" contradicts that reading. Haptics are the natural receiver because they do not disturb others in public and do not occupy gaze. Receiving requires that the event already has a tactile expression; notifications with no mapping can only vanish when silent is on.

Studying it

Measure delivery across the silent toggle: for the same notification, log which channels carried it with sound on and with silent on, and record any event that appeared on no channel at all. Variables include event type, coverage of haptic mapping, and whether the user customized settings. Outcomes include total-loss rate and consistency with the expectation that notifications still arrive when silent.

Where it stops holding

Haptics can only carry binary or few-category information, so complex notifications still need the screen under silence. If the user also enables do-not-disturb or turns haptics off, the receiving channels narrow further and events should be reported as undeliverable rather than disappearing silently. On devices with no vibration motor, silent-mode information must fall to vision.

Applying it

• Ensure notifications that must arrive during silence have a haptic mapping, not one defined only for sound.
• Let users anticipate at the moment of muting which notifications will still arrive.
• For events with both sound and haptics, check that haptics actually fire once silent is on.
• Verification: walk through notification types under silence and measure the proportion that reaches no channel; any total loss means receiving coverage is incomplete.

Related

• Within the group: D3.13.2 On some devices the silent switch also disables haptics, losing information · D3.13.3 Users need separate control over whether haptics follow silent mode
• Adjacent: D2.05.1 Critical information must move to another channel when sound is muted · D2.04.3 Silent contexts need absolute silence, not reduced volume
• Search terms: silent mode · notification channel shift · haptic fallback