[ Package conformance ]
Device & Platform · >=1.0.0
@mhpdev/react-native-haptics
native-seam: the impact/notification/selection/androidHaptics wrappers run from the bundle; the Haptics TurboModule delegates to Peach’s shared expo-haptics navigator.vibrate mapping (same enum string values), so behavior is identical to expo-haptics and there is one source of the vibration logic. calls resolve cleanly when no vibrator is present (and the iOS simulator has no haptics hardware either — the faithful contract)85%
API coverage
No visual conformance cases have been published for this package yet. The registry summary below describes what the compat layer implements.
Working (4)
impact(style: light/medium/heavy/soft/rigid)notification(type: success/warning/error)selection()androidHaptics() — all mapped to navigator.vibrate patterns via the shared expo-haptics implementation
Missing (3)
browsers expose only on/off Vibration (no force/sharpness control) — exact UIFeedbackGenerator texture is approximated by durationidentical to expo-haptics; no perceptible vibration on a device without a vibrator (faithful to the iOS simulatorwhich has none)