Rive on X

Most of the talk reacts to what people have shipped: a game built inside a single Rive file and published with no HTML, CSS or JavaScript, a Quest 3 hologram rendered entirely on the Rive GPU renderer, character and mascot work kept as vectors ("Look it's all VECTORS!"). Some onlookers say they didn't know it could do 3D menus at all, and one calls a browser piece the most impressive thing they have seen there.

Beneath that, 30 people are simply warm about the tool: telling followers it is the one thing to learn this weekend, calling it "insanely good", cheering its arrival in automotive HMI. 10 single out the CLI and agent workflow, saying builds got easier than expected and that prompting with live reload let them spend more time on the creative side. 7 are impressed but uncommitted, planning to test it — one on a Google TV launcher. A minority of 4 enjoy it and find it hard going: "not for the weak", hours of trial and error, every state still to wire.

The frame-rate reports are concrete: a live interaction that "lags like crazy" on an iPhone X, with the person who built it replying that they are working on optimisation for phones; a "pretty powerfull Legion laptop" that lags with no setting offered to fix it; a rebuild noted for the same trouble. One puts it as a cost of the runtime: "rive runtime overhead really is crazy when you just need clean microinteractions."

Smaller, sharper complaints follow. 2 people say AI coding agents don't grasp Rive's features and have to be reminded of them, and suggest building a library of skills about Rive functionality so the agent can draw on it. 2 describe the effort: "wiring up every state is the chore", and a two-hour build spent much of its time on small tweaks to look right from different angles. One person is stuck because compiled .riv files can't be edited and the editable sources weren't shared.

The Unreal talk is about leaving it. One person remembers going all out to build a similar FUI demo in Unreal when the HTC Vive launched and now wants to free up time to dive into Rive; another tells game developers upset about Epic killing off Blueprints in UE6 to keep an eye on Rive. Neither compares the two in detail.

The rest are single voices. One came from Nuke and says they fell in love with Rive. One expected another Figma or Sketch and now calls it "a 2D version of Houdini FX", drawn to the node-based logic. One finalized a design in code first and then tried building it in Rive. One suggests starting an MVP in Masko on a budget and rebuilding it in Rive once the app earns money. What people weigh Rive against is their previous pipeline, not a rival animation tool.

The technique questions follow what people just saw. They ask which Rive feature was used (Auto Trace, Auto Weights, data binding for a costume colour), how strokes export, "vector paths or baked meshes", and whether a character had to be rigged the classic way or was uploaded as 2D images. Others ask how a background scene was put together, how procedural audio works, how shaders were made to load outside the preview build, and why a stack went Rive to React before JUCE. One asks which bottleneck a demo removed.

The smaller questions are about limits and access. 2 people ask whether it is only 2D or can do 3D — ray tracing, realistic textures, built-in scripts for 3D scenes. 2 ask for the source: the demo code, or the original editable files behind published work. 2 want to know how a build gets onto a TV or a headset, and whether that means Unity, Unreal or a custom runtime. One asks whether a project needs a monthly subscription.

The platform wish is about reach beyond the browser: running Rive experiences natively rather than through the Spectacles web browser, a Rive runtime for Lens Studio, and a question about open-sourcing the custom OpenXR runtime used for a Quest 3 demo. All of it comes from people watching mixed-reality work built with the Rive CLI.

The single asks are practical and specific: make the export function free; deepen and make more efficient Rive's integration into the web; a plugin or script "similar to AEUX" to bridge Figma and Rive; an option to preview animations playing in outline mode, which one person calls "next level"; and math.random returning decimal values rather than whole numbers when a scale range is set. One of these sits alongside praise — the web-integration wish opens with liking Rive's potential rather than a complaint.