npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-native-feelback

v0.1.0

Published

Unified semantic haptics for React Native — one API, best-in-class feedback on both iOS and Android

Readme

react-native-feelback

Unified semantic haptics for React Native — one API, best-in-class feedback on both iOS and Android.

Unlike other haptic libraries that treat Android as a second-class citizen, react-native-feelback maps each semantic haptic type to the best available native API on each platform, with graceful degradation on older devices.

What makes this different?

| Feature | expo-haptics | react-native-haptic-feedback | feelback | |---------|-------------|----------------------------|-----------------| | Unified cross-platform API | Separate Android method | iOS-focused mapping | Single API, best per-platform | | Modern Android (API 30+) | Via separate method | Via bridge | Native Turbo Module | | New Architecture | Expo Modules only | No | Turbo Module | | No Expo dependency | No | Yes | Yes | | Semantic types | Partial | Platform-specific | Intent-based |

Platform mapping

| Semantic type | iOS | Android (API 30+) | Android (older) | |--------------|-----|-------------------|-----------------| | tap | Impact (Rigid) | CONTEXT_CLICK | VIRTUAL_KEY | | selection | Selection | VIRTUAL_KEY | VIRTUAL_KEY | | soft | Impact (Soft) | CLOCK_TICK | KEYBOARD_TAP | | heavy | Impact (Heavy) | LONG_PRESS | LONG_PRESS | | success | Notification (Success) | CONFIRM | CLOCK_TICK | | warning | Notification (Warning) | GESTURE_END | LONG_PRESS | | error | Notification (Error) | REJECT | LONG_PRESS |

Installation

npm install react-native-feelback
# or
yarn add react-native-feelback

For iOS, run pod install:

cd ios && pod install

Note: This is a native module — it requires a dev build (not Expo Go).

Usage

import haptics from 'react-native-feelback';

// Semantic methods
haptics.tap();        // Button press
haptics.selection();  // Picker/tab change
haptics.soft();       // Subtle feedback
haptics.heavy();      // Significant action
haptics.success();    // Task completed
haptics.warning();    // Caution
haptics.error();      // Failure

// Or use trigger() with a type string
haptics.trigger('success');

// Global enable/disable (e.g., from user settings)
haptics.setEnabled(false);
haptics.setEnabled(true);

// Check device support
if (haptics.isSupported()) {
  haptics.tap();
}

Named imports

import { tap, success, setEnabled } from 'react-native-feelback';

tap();
success();
setEnabled(false);

With settings integration

import haptics from 'react-native-feelback';
import { useEffect } from 'react';

function useHapticSettings(enabled: boolean) {
  useEffect(() => {
    haptics.setEnabled(enabled);
  }, [enabled]);
}

API

| Method | Description | |--------|-------------| | tap() | Button presses, confirmable actions | | selection() | Picker changes, tab switches, toggles | | soft() | Scroll snaps, subtle value changes | | heavy() | Drop actions, completing significant gestures | | success() | Successful completions (purchase, save) | | warning() | Cautionary feedback (nearing limits) | | error() | Failures and invalid actions | | trigger(type) | Trigger by type string | | isSupported() | Check if device supports haptics | | setEnabled(bool) | Global enable/disable | | isEnabled() | Check if haptics are enabled |

Requirements

  • React Native 0.76+ (New Architecture / Turbo Modules)
  • iOS 13+
  • Android API 24+

Contributing

License

MIT


Made with create-react-native-library