[ Package conformance ]

Device & Platform · >=1.0.0

react-native-haptic-feedback

package-local wrapper registers only the RNHapticFeedback TurboModule; upstream react-native-haptic-feedback JS runs unchanged 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 conformance cases have been published for this package yet. The registry summary below describes what the compat layer implements.

Working (12)

sootsim validated upstream triggerstopisSupportedtriggerPatterngetSystemHapticStatussetEnabledisEnabledimpactHapticFeedbackTypesPatternspattern/PATTERN_CHARSand 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