A haptic design may not reproduce at all on low-end devices

What it is

On low-end devices a haptic design may not degrade—it may fail to reproduce entirely. Short pulses, fine rhythms, or frequency distinctions the design relies on do not exist on that hardware, and users feel a vague buzz or nothing at all.

Why it happens

Failure follows from missing encoding dimensions. Short pulses require fast start and stop, which a coarse motor cannot provide; rhythm discrimination needs a minimum gap below the perceptual floor, and low-end ring-down merges adjacent pulses; frequency distinctions do not exist when the actuator has only amplitude. The result is not weaker strength but vanished structure. A designer validating on premium hardware will not notice, because the same configuration behaves exactly as intended on the reference device.

Studying it

Use the lowest-capability device as the constraint: run the full pattern table on the weakest target model and measure identification rate and output waveform per pattern. Variables include capability tier, pattern complexity, and whether users have prior experience on premium devices. Outcomes include accuracy and the proportion reporting "cannot tell apart," which directly indicates reproduction failure.

Where it stops holding

If a product can require minimum hardware and state it, reproduction failure is moot since unsupported models are never installed. If the pattern table is tiered by capability with simplified versions for low-end models, the failure is avoidable. For premium-only products the constraint does not apply.

Applying it

• Validate against the weakest target model rather than a premium reference device.
• Tier the pattern table by capability, giving low-tier devices simplified but still discriminable substitutes.
• When reproduction is impossible, degrade explicitly to a single cue instead of presenting an unparseable vibration.
• Verification: run full pattern identification on the lowest-capability model; any pattern with a clear accuracy drop needs a substitute.

Related

• Within the group: D3.14.1 Motor types and algorithms make haptics inconsistent across devices · D3.14.3 Cross-device consistency needs degradation plans, not assumed parity
• Adjacent: D3.01.1 Eccentric rotating mass motors start and stop slowly, so short pulses are hard · D3.01.3 Motor type bounds the achievable haptic vocabulary
• Search terms: haptic reproduction · capability floor · device tiers