High-rate haptic feedback needs restraint when battery is low
Aliases: low battery · frequency control · power saving
What it is
When battery is tight, high-rate haptic feedback needs deliberate restraint. Every unit of charge is worth more at low battery, and keypress and scroll feedback accumulate high energy per unit of value, making them the first candidates for reduction.
Why it happens
The logic is a value-density comparison: critical alerts fire rarely but are individually valuable, while high-rate feedback is individually cheap but fires enormously often. Under constrained charge, leaving the resource to the former serves users better. Reductions can also be staged—lower amplitude first, then lower rate, and finally critical events only—so energy falls while the sacrifice stays controllable. If reduction is unpredictable (haptics simply vanish), users read it as a device fault or an app error rather than policy.
Studying it
Compare reduction strategies on energy and experience: under low battery, apply amplitude reduction, rate reduction, and critical-only in turn, measuring additional draw, critical-event identification, and whether users find haptics predictable. Variables include the battery threshold, strategy, and whether users are informed. Include predictability ratings, since unexplained reduction damages trust.
Where it stops holding
On external power or ample charge, reduction is pointless and costs experience for nothing. If the app does not rely on high-rate haptics in the first place, there is little to cut. Where reduction is applied system-wide, apps must align with platform policy so they do not keep requesting haptics the system is already suppressing.
Applying it
- Define staged reduction at battery thresholds: amplitude first, then rate, then critical events only.
- Notify users when reduction takes effect, so weakened haptics are not mistaken for failure.
- Never reduce haptics carrying safety information; preserve their perceptibility first.
- Verification: under low battery, measure additional draw and critical-event identification, and collect user ratings of how predictable the change felt.
Related
- Within the group: D3.15.1 Sustained use of haptic motors measurably drains the battery · D3.15.3 Power cost should factor into whether haptics are used for low-priority cases
- Adjacent: D3.08.2 After overload, users turn off all haptics · K3.04 Battery and performance tradeoffs on mobile devices
- Search terms:
low battery haptics·power saving·frequency reduction