Real-Time in Business Apps: Do You Actually Need It?
We just shipped real-time updates. We've spent engineering effort on making them fast and reliable. Now let's be honest about when they actually matter.
Real-time features are seductive in product design. "See changes instantly" sounds better than "refresh occasionally." And live updates are genuinely useful — but not uniformly, and not always in the ways you'd expect.
When Real-Time Actually Helps
Shared operational lists. When two or more team members are working from the same list — a support queue, a dispatch board, a pipeline in active review — seeing each other's actions in real time prevents duplicate effort and miscommunication. One person claims a ticket; the other sees it claimed without needing to coordinate.
Collaborative record editing. When multiple people occasionally edit the same record, seeing live updates prevents save conflicts and keeps everyone's view current. Not as useful for records that are typically owned by one person.
Time-sensitive status information. A delivery dispatch, an order status board, a production floor view — these benefit from live updates because the freshness of the data directly affects decisions being made now.
Notification and activity feeds. New comments, assigned tasks, status updates that affect your work — these benefit from real-time delivery because the timeliness of the notification is part of its value.
When Real-Time Doesn't Help Much
Individual record work. If you're working on a record by yourself — filling in a form, editing a document, reviewing details — real-time updates of other users' actions on that record are more likely to be an interruption than a benefit.
Low-change-rate data. Records that are updated infrequently don't benefit from real-time updates. The cost (engineering complexity, connection overhead, processing) is real; the benefit is theoretical.
Reporting and analytics. A dashboard that shows business metrics updated in real time sounds impressive. In practice, most business decisions don't require sub-second metric freshness. A refresh on demand is usually sufficient.
The Infrastructure Cost
Real-time is not free. Maintaining persistent connections to every connected client, propagating every change, handling reconnections — this is real infrastructure cost that has to be justified by real user value.
We've built it because the scenarios where it genuinely helps are common in operational business software. But we've thought carefully about which scenarios those are, and we haven't built real-time everywhere just because we could.
Match the capability to the need. That's the design principle.