Open-source project
wix-incubator/react-native-interactable avatar
wix-incubator/react-native-interactable

React Native Interactable: springPoints, gravityPoints, and no maintainer

Experimental implementation of high performance interactable views in React Native

5,174 stars493 forksJavaScriptMIT

At a glance

What is it?
An experimental React Native library that moves gesture driven view physics to the native side so a swipeable card or drawer can settle at 60 FPS. The MIT licensed code ships a full prop set and a Detox suite, but the project asks for a maintainer and has one tagged release from 2017.
Who is it for?
This fits a team that specifically needs gesture driven views, on iOS and Android, and can afford to own an unmaintained dependency. Skip it if you need a release train or a support commitment, and do not plan around the 2017 tag.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 144 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • wix-incubator/react-native-interactable5,174 ★ · +3
Star history
Repository2026-09-232026-11-15
wix-incubator/react-native-interactable5.2k5.2k

3 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

npm install, then react-native link to reach the native side

Two commands get the library into a project, and the second one is what makes the physics work at all:

bash
npm install react-native-interactable --save
react-native link react-native-interactable

RN 0.40 and above is the stated floor. Linking by hand is also covered, with the Xcode project sitting inside the package at `node_modules/react-native-interactable/ios/Interactable.xcodeproj`, and iOS users can take the CocoaPods route by adding one line to the Podfile and running `pod update`:

ruby
pod 'Interactable', :path => '../node_modules/react-native-interactable'

One detail to notice in package.json: the peer dependencies set a floor and no ceiling, react `>= 15.4.1` and react-native `>= 0.40.0`. Nothing there names a version the library was verified against, and the linking command in the docs belongs to the React Native generation that had it. That combination means the manifest will accept a React Native version the instructions were never rewritten for.

One tag from 2017, a 2.0.1 in package.json, and a maintainer request

Version numbers here have to be read twice. The only tagged release is v0.1.3 from 2017-09-01, while package.json declares 2.0.1, and what lands in your node_modules is the npm package rather than the tag. So planning an upgrade path around a git release is a mistake: the tree moved on and the release history did not. The second section of the README is a note headed LOOKING FOR A MAINTAINER, saying the team loves the project but does not have enough time to work on it, and giving an address at wix.com to volunteer. Commits are still landing, since the last push to master is dated 2026-06-24. The fair reading is that the code is not frozen while the maintainer situation is open, which is a different problem from an abandoned library and a worse one than a version you can trust.

Springs and gravity wells are declared in JavaScript, solved natively

The design exists because of the bridge. The README says plainly that the async React Native bridge carries a performance penalty, that this is what stops JavaScript animations from running at 60 FPS, and that Animated answers it by declaring animations in JavaScript while a native driver executes them on the other side. Interactions go past animation, since the UI has to keep answering gestures, so this library drives them with a physics engine on the native side. The props are the knobs:

jsx
springPoints={[{x: 0, tension: 6000, damping: 0.5, influenceArea: {left: 0}}]}
jsx
gravityPoints={[{x: 0, y: 0, strength: 8000, falloff: 40, damping: 0.5}]}

A spring pins the view center to a point with tension and damping, a gravity well attracts or repels it with strength and falloff, friction areas damp movement inside a region, and alert areas fire events when the center enters or leaves one. You declare the shape of the simulation once and the per frame work stays off the JavaScript thread.

The simulator flatters the framerate the library is built for

The demo is a playground project in the repository, with a swipeable card, a drawer, a collapsible header and chat heads under Basic examples, and harder combinations under Real life example. You run it from the root:

bash
npm start
npm run ios

Then comes the instruction that decides how you evaluate this: use a real device, not a simulator, because the simulator has poor performance and the framerate is not like the real thing. That is the honest cost of the library. The number it is built around is 60 FPS under continuous gesture interaction, and that number cannot be judged on the machine most people try first. A team weighing this for a shipping app needs a physical device in the loop from the first spike, because the same code can look broken on a simulator without being broken anywhere else.

npm test is a colon, so the real suite is Detox on two platforms

The script list in package.json holds the testing story, and it opens with a surprise: `test` is set to a colon, so `npm test` finishes without running anything at all. Coverage is end to end, through Detox 18, split by target. `e2e:ios` runs the ios.sim.release configuration with debug synchronization, `e2e:android` builds and runs android.emu.release with verbose logging, `e2e:android:ci` adds `--headless` for a build machine, and `e2e:ios-multi` forwards `-w 2` for two workers. Builds come from `build:ios` and `build:android`, both feeding Detox build configurations, and an `e2e/` directory at the root holds the specs. A jest preset is configured, so the unit test side is set up but not attached to the test script. The consequence for a team is blunt: a passing npm test tells you nothing about this library.

startOnFront is Android only and the prop contract lives in PROPS.md

The README prop list covers `snapPoints`, `springPoints`, `gravityPoints`, `frictionAreas`, `alertAreas`, `horizontalOnly`, `startOnFront` and `verticalOnly`, and links to the full reference for all props in PROPS.md at the root of the repository. One entry carries its platform caveat in the description: `startOnFront` is marked Android only and makes the view call `bringToFront`, so a component shared between platforms has to guard it. Around that there is a `typings/` directory at the root and a devDependency on `@types/react-native`, so TypeScript consumers had something to work with, plus SUPPORT.md for the support policy and UX-INSPIRATIONS.md behind the demo. The practical rule that follows: treat PROPS.md as the API contract, because the README links there for the full reference for all props.

Editorial conclusion

This fits a team that specifically needs gesture driven views, on iOS and Android, and can afford to own an unmaintained dependency. Skip it if you need a release train or a support commitment, and do not plan around the 2017 tag. Before adopting, read PROPS.md rather than the README, check which version npm actually serves, and confirm the linking step still matches the React Native version you run.

Frequently asked questions

What React Native version does react-native-interactable require?

The README states RN 0.40 and above. The peer dependencies in package.json ask for react >= 15.4.1 and react-native >= 0.40.0, and set no upper bound.

How do I install and link react-native-interactable?

Run npm install react-native-interactable --save, then react-native link react-native-interactable to hook up the native module. On iOS you can instead add pod 'Interactable', :path => '../node_modules/react-native-interactable' to your Podfile and run pod update.

What does Interactable.View add to a React Native view?

It wraps a view so gestures drive a physics engine on the native side, with snapPoints, springPoints, gravityPoints, frictionAreas and alertAreas declared in JavaScript. The reason is the async bridge, which stops JavaScript animations from holding 60 FPS.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. wix-incubator/react-native-interactable on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/wix-incubator-react-native-interactable.svg)](https://hysenlabs.com/projects/wix-incubator-react-native-interactable)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/wix-incubator-react-native-interactable.svg)](https://hysenlabs.com/projects/wix-incubator-react-native-interactable)

Was this useful?