Users need separate control over whether haptics follow silent mode

What it is

Users should be able to choose whether haptics follow silent mode. Some want complete quiet in silent mode, vibration included; others rely on vibration to receive information without disturbing anyone. Hard-binding the two, in either direction, disappoints one of those groups.

Why it happens

Both needs are legitimate: in a meeting or cinema, even vibration may be noticed or prohibited; on a commute or during exercise, vibration is precisely the substitute for a ringtone. Coupling is common because it is simpler to implement—one switch, one state bit—but the cost is that users cannot express their real preference. Independent control also lowers wholesale disabling, because dissatisfied users can turn off one class rather than all output. The default value matters most, since it governs the majority who never open settings.

Studying it

Study preference distribution and switching behavior: offer independent control and record the combinations users choose (silent with haptics, silent without, and so on) and how those change over time. Variables include the default combination, context, and user activity. Outcomes include the preference distribution, switching frequency, and satisfaction; frequent switching signals that needs genuinely vary by situation.

Where it stops holding

If the platform provides no independent haptic state, apps must build their own setting and manage precedence against the system state. When a haptic class is a safety alert, allowing it to be disabled under silence deserves care and may need a stated consequence. If users rarely open settings, the default effectively determines most people's experience, so the default should lean toward keeping critical haptics during silence.

Applying it

• Offer a haptic switch independent of silent mode and show which combination is currently active.
• Default to keeping critical haptics during silence while allowing full disabling.
• Persist the chosen combination across updates where permissions allow.
• Verification: tabulate the distribution of chosen combinations and later switching; if many users switch repeatedly, the default or context adaptation needs work.

Related

• Within the group: D3.13.1 Silent mode is expected to hand notification duty to haptics · D3.13.2 On some devices the silent switch also disables haptics, losing information
• Adjacent: D3.12.1 Haptics need a global off switch rather than forced always-on · D2.11.3 Category control needs its own entry point, independent of system mute
• Search terms: haptic and silent mode · decoupled settings · user preference