Proof

react-native-haptic-feedback

real upstream package — not intercepted. the app's react-native-haptic-feedback JS runs over the RNHapticFeedback TurboModule against the browser vibration API where available. full upstream API surface — every documented entry point lands on either real navigator.vibrate work or correct unavailable shape.

93%

API coverage

No visual proof cases have been published for this package yet. The registry summary below describes what the compat layer implements.

Working

sootsim validated upstream trigger, stop, isSupported, triggerPattern, getSystemHapticStatus, setEnabled, isEnabled, impact, HapticFeedbackTypes, Patterns, pattern/PATTERN_CHARS, and TouchableHaptic; RNHapticFeedback TurboModule uses navigator.vibrate for trigger/triggerPattern/stop and reports browser support shape

Missing (3)

actual Core Haptics/UIKit haptic engineAHAP file playbackhardware-specific intensity/sharpness rendering — these are unavailable on web (browser vibration API only honors duration patterns); apps that gate on isSupported take the no-haptic branch correctly