How Map2Point's live map actually works

"Real-time" gets used loosely in mapping apps — sometimes it means updates every few seconds, sometimes every 30. We wanted Map2Point's shared map to feel the way a live map should feel: a vehicle moves, and it moves on every other screen almost immediately, not after a noticeable lag.

Broadcast, not polling

Every vehicle that's actively sharing publishes its position over a private, authorized real-time channel scoped to that specific vehicle — not a shared firehose every participant has to filter, and not a REST endpoint anyone has to poll. The moment a new position comes in, it's pushed to every subscribed device. No refresh, no fixed interval, no guessing how stale the dot on the map actually is.

Position updates are also persisted to the database on a slightly slower cadence, independent of the live broadcast. That's what makes it possible to reconnect a device that was backgrounded for ten minutes and have it catch up instantly, instead of waiting for the next live update to happen to arrive.

Smooth movement, honestly

A raw GPS feed is jumpy — accuracy varies, samples arrive irregularly, and a vehicle sitting at a red light can look like it's drifting a few meters in every direction. Rendering that literally on a map looks broken, even though the underlying data is fine. So positions are interpolated between samples rather than snapped, and a vehicle's displayed "moving" or "stopped" state is smoothed rather than reacting to every single noisy sample — the difference between a map that looks alive and one that looks glitchy, using the exact same underlying GPS data.

What "offline" actually means

A vehicle doesn't just vanish when its signal drops. Map2Point tracks how long it's been since a real update arrived, and once that crosses a threshold, the vehicle is explicitly marked offline on everyone's map — not silently frozen in its last position with no indication anything's wrong. When it reconnects, its marker doesn't teleport; it catches up smoothly to wherever it actually is now, so the rest of the group can see it was in a dead zone, not that something broke.

Why this matters more than it sounds

None of this is visible when it's working — which is exactly the point. The times it's supposed to be noticeable are the times something actually needs attention: a vehicle that's really fallen behind, a phone that's really lost signal, a stop that really needs everyone's input. Getting the "boring" real-time plumbing right is what makes the alerts built on top of it trustworthy instead of noisy.