Rive lets view models live at the file level, not just one artboard
By Steven Van ·
Editor build 0.8.5321 adds Global View Models so multi-artboard files can share one data source instead of duplicating it per artboard.
Rive has shipped Editor 0.8.5321, and the headline feature changes how data can be structured across a file: Global View Models. Until now, a view model belonged to a single artboard. In this build, a view model can live at the file level instead, available everywhere rather than scoped to the artboard it was created on.
What Global View Models unlock
Create one from the Data panel's + menu under View Model → Global, and its properties can be bound from any artboard or component in the file. That matters for anyone building multi-artboard files, think a design system of components, a multi-screen app flow, or a set of variant states, where the same underlying data (a user's name, a theme setting, a progress value) needs to drive several artboards at once. Before this release, keeping that data in sync meant duplicating view models per artboard or wiring up workarounds. Now one global model can be the single source of truth, bound wherever it's needed.
Where this fits in Rive's data binding model
View models are the backbone of Rive's data binding system, they define the structure of the data that drives a file's state machines, text, and component properties at runtime. Rive has been building out this system steadily, with recent editor builds adding data table views for large view models and reworking the State Machine UI to give data panels more room. Global scope is a natural next step: it takes the data layer from per-artboard to file-wide, which is the direction most production Rive files, especially design-system style projects with many linked components, actually need to scale.
Part of a fast release cadence
0.8.5321 continues Rive's habit of shipping frequent, focused editor builds rather than big infrequent updates, following recent releases like 0.8.5275 just days earlier. Small, fast releases mean structural changes like this reach production files quickly instead of waiting on a larger version bump.
Where to read the full notes
The complete changelog for this build is on the announcement post, and Rive keeps a running history of editor releases at rive.app/changelog.
Sources: Rive Community, Rive Changelog.