There are two ways to get designed motion into a React Native app. One is to rebuild it by hand with a library such as Reanimated. The other is to play a file made in a design tool through a runtime. ExodeUI takes the second approach.
You design the component in ExodeUI with its states, transitions, spring physics and logic. The result is one .exode JSON file. In your app, the ExodeUI React Native runtime plays that file, and your code controls it: set a boolean input when a request is loading, fire a trigger when it succeeds, or set a number from a slider or scroll position. The animation can also send events back to your code.
This means a designer can change timing, colours or a state without a developer rewriting animation code, as long as the inputs and events stay the same. Because the file is shared, the same component can be used in a React web app, a SwiftUI app or a Flutter app.
If you want hand-written code instead, for example because you need full control or have strict bundle limits, Reanimated remains the standard choice in React Native. Some teams use both: hand-written motion for core navigation and runtime files for richer components.
As with any runtime, test on the devices you support, especially older Android phones, before relying on it for critical screens.