Rive for vehicles and devices
Rive is the whole engine for instrument clusters, center displays, companion apps, and custom hardware. It runs fast on the GPU already in the car, and the runtimes have no per-unit fees. Your agent builds the UI with the Rive CLI, and designers refine it in the Rive Editor.
Your whole engine
Layout, animation, state machines, data binding, text, and 3D in one runtime, with nothing else to license underneath.
Fast on car hardware
The Rive Renderer draws vector, raster, and 3D on the GPU already in the car, with crisp text at any size.
No per-unit fees
No royalties and no per-unit runtime fees. The runtimes are open source under the MIT license.
Vehicle interface
An unofficial concept made for BMW, an investor in Rive: a 3D vehicle, map, and media player, built in 24 hours. The source is open.
Instrument clusters
Clusters with animation, responsive layouts, live vehicle data, and localized text, in one file.
Center displays
Climate, media, and settings screens connected to vehicle data. The file is the UI that ships, not a mockup.
Rive Editor
Designers and animators refine every screen by hand in the Rive Editor, an interactive design tool with timelines, state machines, data binding, responsive layouts, and 3D. What they build is the UI that ships, not a mockup.
3D
Build 3D maps, vehicles, and scenes with GPU Canvas, next to your 2D UI in the same file.
Data Binding
Bind speed, range, media, and other vehicle signals to the design. The UI reacts in real time.
Layouts
One responsive design fits every screen, from the cluster to the center display to the phone.
State Machine
Design drive modes, alerts, and menus as states and transitions, with no code.
Graph Editor
Shape every motion curve by hand, so needles, gauges, and menus move exactly the way you want.
Libraries
Share components across screens and model lines. Update the library, and every file that uses it follows.
Investors
“By merging design and development into a unified workflow, Rive unlocks faster time to market, higher-quality UI, and frees up valuable developer time, reducing cost. We believe this sets a new standard for the next generation of interactive design.”
Kasper Sage, Managing Partner, BMW i Ventures
Faster time to market
Designers, developers, and agents work on the same file, so there’s no handoff and no rebuild in code for each screen.
Higher-quality UI
Vector, raster, and 3D in one scene, drawn by the Rive Renderer on the GPU already in the car.
Lower cost
No revenue share, no runtime fees, and MIT open-source runtimes. One file covers the cluster, the center display, and the companion app, so there’s one thing to build and maintain.
How to get started
Your agent builds it. You test it in the CLI preview window and keep directing it until it’s right.
01 Paste the prompt
Paste it into Claude Code, Codex, Cursor, or any coding agent. The agent installs the Rive CLI for you.
02 Describe the screen
Ask for a cluster, a center display, or a companion app screen. Your agent writes the Rive file and shows it in the CLI preview window.
03 Connect vehicle data
Your agent binds speed, range, media, and other signals to the file and adds the Rive runtime to your platform.
04 Keep designing in the Editor
Push the file to your Rive account and open it in the Rive Editor. Refine layout, motion, and states with professional design and animation tools. Needs a free Rive account.
FAQ
Common questions about building vehicle and device UI with Rive.
Which platforms does Rive run on?
Rive runs as the whole engine on custom platforms through its open-source C++ runtime, plus Android and the web. The same file also runs in companion apps on iOS and Android, and inside Unity or Unreal if your team already uses them.
Is this production UI or a prototype?
Production. The Rive file is the UI that ships, connected to real data, not a mockup that engineers rebuild in code.
Can one file handle many languages?
Yes. Rive text supports dynamic, localized strings, so one file can serve every market.
Can I start from my Figma designs?
Yes. Point your coding agent at your Figma file and it rebuilds your screens in Rive as working UI, with reusable components, data binding, and animated transitions. See Figma to Rive for the full workflow.
How does the UI get vehicle data?
Through data binding. Your code sets values like speed, range, or the current track, and the file reacts. Your code can also listen for values the file changes.
How do I license Rive for a production vehicle?
Talk to our sales team about Rive Enterprise. There are no royalties or per-unit runtime fees, and the runtimes are open source under the MIT license.
Join our newsletter
Get all the latest Rive news delivered to your inbox.