State Machines: Rive vs ExodeUI
Rive invented the visual state machine for designers. ExodeUI runs the same concept through to production code.
Direct Answer
Rive's State Machine is the industry benchmark for interactive animation logic — inputs, layers, transitions, and listeners all authored visually. ExodeUI's Visual Logic Nodes cover the same ground and push further: nodes can bind to real application data, run physics triggers, and compile to React/Swift code. The decisive difference is where the logic lives: inside Rive's binary, or in open JSON your whole team — and your AI tools — can read.
1. Where the Logic Lives
A Rive state machine is embedded in the .riv file. At runtime you address it by name and feed it inputs — powerful, but opaque: code review, diffing, and automated testing of the logic itself aren't possible.
ExodeUI logic is serialized as structured JSON. Engineers can review a logic diff in a pull request, generate tests against node graphs, or let an MCP-connected AI agent propose edits. The logic becomes a first-class citizen of your codebase.
- Visual states, events & transitions — no listener boilerplate.
- Data binding to live app data, not just animation inputs.
- Versionable, diffable, AI-editable logic graphs.
2. Feature-by-Feature
| Capability | Rive | ExodeUI |
|---|---|---|
| Visual state authoring | ✅ Best-in-class | ✅ Visual Logic Nodes |
| Logic in code review | ❌ Binary-embedded | ✅ Open JSON diffs |
| Runtime data binding | ✅ ViewModel inputs | ✅ Native app data |
| AI-editable logic | ⚠️ Limited (via AI features in editor) | ✅ MCP-native |