DEV Community

Cover image for Rive vs Exode: Two Very Different Answers to the Same Word, 'State Machine'
shinoj cm
shinoj cm

Posted on

Rive vs Exode: Two Very Different Answers to the Same Word, 'State Machine'

"State machine" has become one of those words that means whatever the vendor needs it to mean. Rive and Exode both use it. They are not describing the same thing, and understanding the difference will save you a migration.

What Rive means by state machine

Rive's state machine lives inside an animation. You have a character or a vector artwork, and you define states for the artwork:

  • idle → hover when the pointer enters
  • idle → pressed on click
  • any → success when a boolean input flips

Inputs are typed, transitions have conditions and blend durations, and the runtime advances the machine every frame. It is excellent. It is also scoped to the artboard: the machine cannot position your page, choose a layout, or read from your application store unless you pass values in as inputs.

That is not a limitation of Rive's engineering. It is the correct scope for its job: making a .riv artwork react.

What Exode means by state machine

Exode's state machine sits above the scene, not inside one piece of art. It owns application-level state — idle, validating, submitting, error, success — and it can:

  • drive multiple objects at once, not just one artwork
  • read and write typed variables (boolean, number, string, colour)
  • fire listeners that trigger animations, navigation, or a webhook
  • advance in the exported component, not in a separate player

In practice it looks like the difference between animating a button and building a checkout.

The test that separates them

Ask: if the network fails, whose job is it to show the error state?

With Rive, your React code catches the error, sets a boolean input via the runtime API, and Rive transitions to the error artwork. That works, and it is a reasonable architecture. But the logic is split: half in the state machine, half in your component.

With Exode, the failure event can be an input on the same machine that owns submitting and success, and the compiled component exposes one interface:

<CheckoutCard
  price={price}
  status={status}            // 'idle' | 'validating' | 'error' | 'success'
  onAddToCart={handleAdd}
/>
Enter fullscreen mode Exit fullscreen mode

The machine that designed the transition is the machine that runs it.

Where Rive wins, clearly

I want to be precise here because the internet is full of vague swipes.

Runtime size. Rive's runtime is small and battle-tested. It ships in games, on TVs, in mobile apps. If your constraint is "add 40 KB and nothing else", Rive has years of optimisation behind it. Exode's current engine bundle is larger — the team publishes its own benchmark work, including the lazy-loading plan to get the base runtime down, and I would not pretend the number is competitive today.

Character art. Mesh deformation, bone weighting, and the professional workflows around rigging a character are more mature in Rive. Exode shipped bones and IK, and its rigging audit lists the gaps it closed, but Rive has more years of artists stress-testing it.

Game engines. Rive has official Unity, Unreal, Godot and Defold paths. If your target is a game engine, that is a strong reason to pick Rive.

Proven production history. Rive is embedded in a lot of shipped software. That matters when you are choosing infrastructure.

Where Exode wins, clearly

Layout. This is the big one. Rive is a stage. Exode has real flexbox, grid, constraints and breakpoints that mirror CSS. Building a responsive pricing table in Rive means positioning objects on a canvas. In Exode it means setting layout rules that survive a viewport change.

DOM semantics. A Rive artwork renders into a canvas. A button inside it is not a <button>. It has no focus ring, no tab order, no accessible name. Exode compiles to real elements, so keyboard navigation, screen readers and form libraries work.

Open format. .exode is JSON with a published schema. You can diff it in a pull request, review a motion change the way you review code, and let an agent edit it. .riv is a compact binary; that is a deliberate and defensible choice for a runtime format, but it is not reviewable.

Data binding. Charts, tables and lists in Exode can bind to JSON payloads. A Rive artwork cannot render your live sales data without you generating the artwork dynamically.

Code output. Exode emits framework components (React, Vue, Svelte, Solid, Angular, Swift, Kotlin, React Native) rather than a player you embed. That is its whole architectural bet.

A concrete comparison

I built the same "add to cart" interaction in both.

In Rive: an artboard with a card, a button, and three states. It looked great. The click handler lived in React and called stateMachine.inputs.addFired = true. The success state was another input. Total integration: a canvas element, a runtime hook, and a bridge layer that mirrored React state into Rive inputs and back out through events.

In Exode: one state machine, four states, two inputs, one trigger. The click handler lived on the object as an interaction, and the failure path was a transition. Export produced a component whose props were the same inputs.

Both worked. The Rive version was smaller and the animation was more polished, because Rive's art tools are better for that. The Exode version had less glue code and produced a component my team could ship without a bridge.

How to choose

Pick Rive if: the artefact is artwork, it needs to be tiny, it runs in a game engine or a canvas-first context, or you have artists who already know the tool.

Pick Exode if: the artefact is an interface, it needs layout, accessibility and data, and you want the design file to compile to the component your app ships.

Do not pick either if: a CSS transition and a useState would solve it. Seriously. Half the state machines I see in the wild are three booleans wearing a costume.


I work on Exode's runtime. Rive is a good tool and you should use it where it fits. If you want to see the interface-side workflow, exodeui.com has a free tier.

Top comments (0)