Rive · Interactive graphics
State machines that run everywhere data lives
High-fidelity Rive scenes wired to live telemetry — one .riv asset across Flutter, Swift, Kotlin, WebGL2, and C++ embedded displays. Design owns the motion; engineering owns the inputs.
- Number and boolean State Machine inputs as a strict contract between backend telemetry and visual state
- rive_native + Impeller on Flutter for fluid multi-platform shells around the same interactive scene
- Native Swift and Kotlin runtimes for OS-level integration without web wrapper overhead
- WebGL2 and C++ embedded paths so the same graphic ships to portals and in-home IoT surfaces
Runtime surfaces
FlutterSwiftKotlinWebGL2C++ embedded
How I work Rive
I treat Rive state machines as a contract between design and engineering — number and boolean inputs driven by live telemetry, one .riv asset across Flutter, Swift, Kotlin, WebGL2, and C++ embedded displays.
The Home Energy Dashboard lab shows the pattern: high-fidelity motion owned by design, inputs owned by the backend, runtimes chosen per surface.
- State Machine inputs as a strict telemetry → visual contract
- rive_native + Impeller on Flutter multi-platform shells
- Native Swift / Kotlin without web-wrapper overhead
- WebGL2 and C++ embedded paths for portals and IoT