Skip to content

Instantly share code, notes, and snippets.

@JonnyBurger
Created March 31, 2025 06:42
Show Gist options
  • Save JonnyBurger/095428e9edbefe927c34551a4bf981ae to your computer and use it in GitHub Desktop.
Save JonnyBurger/095428e9edbefe927c34551a4bf981ae to your computer and use it in GitHub Desktop.
AI-generated docs draft: No plans to support React Native due to performance issues.

johanx03 - 3/28/2025, 10:20:01 PM

Will you bring back support for react native?

jonnyburger - 3/31/2025, 6:41:55 AM

it's not planned to add support for react native. while we previously prototyped this, we realized that with the model of re-rendering on every frame, we could not achieve the high performance as we can on the web. a framework like remotion for react native would ideally work with reanimated or another way to avoid re-renders on react native. this would mean the framework and the components would have to be architected quite differently that that they are right now.

you can also consider experimenting with remotion player using expo dom components, a proof of concept is here. EvanBacon/expo-dom-components-canary-example#4

Technical Note on React Native Support

Problem

Support for React Native is currently not planned due to performance issues. The main culprit is the model of re-rendering on every frame, which prevents achieving the high performance levels that are possible on the web.

Reasons

  • The existing framework components are not optimized for the React Native environment.
  • Significant architectural changes would be required to support frameworks like Remotion within React Native effectively.

Proposed Solution

  1. Explore the use of Remotion with React Native by integrating it with Reanimated or alternative methods to reduce re-renders.
  2. Experiment with the Remotion player utilizing Expo DOM components. A proof of concept is available here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment