Live features
Update screens live when data changes
Let signed-in people see new and changed records the moment they are saved, without refreshing the page.
Live updates let a screen refresh itself when the data it shows changes, for example a shared task list or a booking calendar several people use at once. It works in the preview and in the published app, for people who are signed in. It is an add-on the build AI turns on when your app needs it.
When to use it
- Several people look at the same records and must see each other's changes.
- A dashboard should follow new orders or messages as they arrive.
For rooms where people act together in real time, like a game or a whiteboard, use live sessions instead.
How to use it
Ask the build AI, or select Turn on next to Live updates in Runtime, which asks it for you.
Make the team task list update live, so when someone adds, edits or completes a task, everyone who has the list open sees it straight away.
The app needs sign-in; if it doesn't have it yet, the build AI adds it first. Access rules still apply, so a person gets live changes only to records they may read.
To check it, open the app in two browsers, signed in as two people, change a record in one, and see it change in the other. After a lost connection the screen catches up on what it missed.
Plans and limits
The same on every plan. Live updates reach signed-in people only; signed-out visitors see the data as it was when the page loaded.
Troubleshooting
Changes don't appear until a refresh. Check the person is signed in and may read the changed record. Ask the build AI to confirm the screen subscribes to that table.
A screen stops following changes after a long time offline. It reloads the list when it reconnects; if it doesn't, refresh once and tell the build AI what you saw.