Why people leave Rive
The reasons are usually practical rather than ideological. Rive is free to build with, but free exports play a Rive splash screen, so shipping anything real means Cadet at $9 per seat per month. Cadet is capped at three seats, and Voyager, where unlimited files and libraries actually start, is $32 per seat per month. Enterprise is $120 per seat per month and is required by their terms once annual revenue passes $10 million.
The second reason is the file. A .riv is a packed binary. You can ship it, but you cannot read it, diff it, review it in a pull request, or fix a value by hand at 2am. ExodeUI stores components as .exode JSON (compiled to .bexode for shipping), so the same file is both the source and the build artefact.
The mapping, input by input
If your Rive file leans on state machines rather than heavy character rigging, the mental model transfers almost unchanged. These are the pieces and where they land.
| In Rive | In ExodeUI | Notes |
|---|---|---|
| .riv file | .exode JSON, or compiled .bexode | The JSON version is readable and diffable in git |
| Trigger input | Trigger input | Fires a transition on demand |
| Boolean input | Boolean input | True/false conditions on transitions |
| Number input | Number input | Drives blend values, progress and ranges |
| Text / data binding | Text input | Data binding itself is not imported: set the value from your code |
| State machine | State machine | States, transitions and conditions import |
| Blend state | Plain state | Flattened on import, so re-add the blend by hand if you need it |
| Listener (pointer, hover) | Object interaction rules | Rebuild these; listeners are not imported |
| Scripting | Node logic and inputs | No scripting layer. Logic is nodes plus state conditions |
| Bones, IK, constraints | Imported | Arrives as editable layers, not a flat image |
| Unity / Unreal / C++ runtime | Not available | Runtimes here cover React, Vue, Svelte, Angular, Solid, React Native, SwiftUI and Flutter |
What does not come across
Be specific about this before you commit. The importer measures itself against the Rive renderer on a corpus of 387 open-source rive-runtime test files, and lands close on 238 of them. That is a real number, not a marketing one, and the files it misses are mostly the ones below.
Data binding, scripting, artboard lists, listeners, draw rules, text modifiers, blend states, and layout grid and wrap are not converted. Blend states come through as ordinary states, so the visuals survive but the intensity behaviour does not. Text modifiers and draw rules have no equivalent yet. If your component depends on two or three of these, converting may cost more than rebuilding.
What your code looks like afterwards
The runtime takes the file plus the inputs your component needs, and reports events back to your app. React, Vue, Flutter, SwiftUI, React Native and the others all follow the same shape: one canvas component, one file, inputs in, events out.
import { ExodeUICanvas } from 'exodeui';
// toggle.bexode lives in /public
export function Toggle() {
return (
<ExodeUICanvas
src="/toggle.bexode"
fit="Layout"
autoPlay
interactive
inputs={{ checked: true }}
onTrigger={(name) => {
// fires the events you defined in the file
}}
style={{ width: '100%', height: 64 }}
/>
);
}Nothing is code-generated. The file stays the source of truth, so a designer can change the spring in the editor without a merge conflict in a component file.
What it costs after the move
Rive charges per seat and gates the splash screen. ExodeUI Professional is $5 per month billed yearly, and the Community plan is free. Seat maths is only part of it, though: if you were on Cadet mainly to remove the splash screen from a handful of components, the move pays for itself immediately. If you were on Voyager for libraries and embed hosting, check that you do not need the hosting part, because we do not sell a CDN.
We make ExodeUI, so treat its column as the vendor talking about its own product. The rebuild estimate below is the number most people underestimate.
Then count the rebuild. A state-machine-driven UI component usually takes an afternoon. A character rig with meshes and heavy blend work can take much longer, and may not be worth moving at all.
| Rive | ExodeUI | |
|---|---|---|
| Free plan | $0, exports play a Rive splash screen | $0 Community plan |
| Entry paid plan | $9 / seat / month (Cadet, 3 seats max) | $5 / month billed yearly (Professional) |
| Mid plan | $32 / seat / month (Voyager, 25 seats max) | — |
| Enterprise | $120 / seat / month, required above $10M annual revenue | Contact us |
| Source file | Binary .riv, plus a text source format via their CLI | Open .exode JSON, compiled to .bexode |
When you should stay on Rive
Rive is genuinely better for some of this work and we are not going to pretend otherwise. If you are rigging characters with meshes and heavy blend states, Rive has years of tooling we do not match. If your target is Unity, Unreal, consoles or C++, Rive has runtimes and we do not.
Rive also has long-term support agreements and automotive customers, and a stock marketplace. If those are why you picked it, moving is the wrong call. The honest split is that Rive is a graphics and character tool that also does UI, and ExodeUI is a UI tool that does motion and logic.