Design Real Time Data Refresh
Data & Dashboards · real-time, dashboards, status
Updated 2026-07-28
- Ask whether live updates help the task. Monitoring an incident needs them, and reading a monthly report does not, where constant movement is only a distraction.
- Never move content under the user's cursor. Inserting a row at the top while someone is clicking causes the wrong action on the wrong item.
- Buffer instead of interrupting. Collect new items and offer them with a "3 new items" control the user presses when they are ready.
- Update values in place with a brief, quiet highlight. A flash that draws the eye once is useful, and a permanently animated number is exhausting.
- Freeze while the user is working. Selection, an open menu, an in-progress edit, or an active sort should pause updates until the interaction ends.
- Show the connection state honestly. Live, reconnecting, and disconnected are three different situations and only one of them means the numbers can be trusted.
- Choose a refresh rate the data deserves. Polling every second for a metric that changes hourly is expensive for the server and pointless for the reader.
- Back off when the tab is hidden and catch up when it returns, rather than running a full-rate stream nobody is watching.
Live data is only valuable when the reader can still read it, so stability matters as much as freshness.
Related guides