wix-incubator/react-native-interactable

Experimental implementation of high performance interactable views in React Native

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 13th, 2026
Created on January 26th, 2017
Open Issues & Pull Requests: 88 (+0)
GitHub issues: Enabled
Number of forks: 495
Total Stargazers: 5,172 (+0)
Total Subscribers: 313 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 26.9 days
Mean response time: 118.5 days
90th percentile: 210.0 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 655 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

React Native Interactable is a library for building high-performance interactable views in React Native that respond fluidly to user gestures at 60 frames per second.

The library addresses the challenge of executing complex physical interactions smoothly on mobile devices despite the performance overhead of the React Native bridge. It uses a declarative API paired with a native physics engine that runs on the device side, allowing interactions like swiping, dragging, snapping, and spring animations to execute at consistent frame rates without blocking the JavaScript thread. Rather than shuttling gesture data back and forth across the bridge on every frame, the physics simulation runs natively while JavaScript declares the interaction parameters and constraints.

The tool suits projects that need sophisticated gesture-driven UI components with natural physical behavior—swipeable cards, draggable drawers, collapsible headers, and floating chat heads are the primary use cases. It works best when you need interactions that feel responsive and spring-like rather than stiff or delayed. Developers should adopt it if their app requires complex touch interactions that must maintain smooth animation at 60 FPS and they are willing to work with the native linking requirements for iOS and Android.

The project is currently seeking a maintainer and does not have active development resources allocated to it. The codebase is stable but unmaintained, meaning bug fixes and compatibility updates with newer React Native versions are not guaranteed. Anyone considering adoption should evaluate whether the lack of active maintenance aligns with their project's long-term needs and whether they can contribute fixes internally if required.