External accessories are usually weaker than built-in motors

What it is

Accessories usually deliver less haptic capability than the device's built-in motor. Headphones, styluses, controllers, and wearables have constrained motor size and power, so both strength and temporal precision fall below the phone body. When output routes to an accessory, a design that holds on the main device can weaken noticeably.

Why it happens

The limits are physical: small accessory volume means limited motor and battery capacity, and mechanical coupling is weaker—a stylus contacts the hand over a small area, headphones couple to the ear and skull differently than a hand grip, and energy distributes quite differently. Accessories also usually receive commands over a wireless link, and the added latency can disturb timing-sensitive patterns. Accessory haptics therefore suit simple confirmation better than reproducing rich temporal structure.

Studying it

Compare output on the main device and the accessory within one system: measure perceptible strength, minimum discriminable gap, and identification of critical patterns on each. Variables include accessory type, connection (wired or wireless), and wear state. Include latency, which directly affects timing-dependent patterns. Record routing logic so the test confirms output actually reached the intended device.

Where it stops holding

If users always use the accessory and never switch, the design can be calibrated to it and the problem reduces to single-device adaptation. If the accessory carries its own high-performance haptic unit, the gap narrows, though power and volume constraints persist. When the accessory merely relays haptics rather than rendering them, experience depends on which end renders.

Applying it

• Specify when haptic output routes to the accessory and validate critical patterns against accessory capability.
• Prefer simple, longer-duration patterns on accessories and avoid reliance on fine temporal structure.
• Keep semantics consistent across a routing switch so one event does not mean different things on device and accessory.
• Verification: measure detection and identification of critical events on both, and provide accessory-specific substitutes for patterns that diverge.

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.02.2 Perceived intensity depends on how the device is held · K2.04 Capability negotiation and degradation with external devices
• Search terms: accessory haptics · wireless latency · capability negotiation