Real-time operations
RouteFlow
Live worker tracking, multi-stop routing, ETA recalculation, and shareable public tracking views.
RouteFlow is not a map demo. It is an operations layer built around the questions a manager actually has: where is the worker, what comes next, and what does the current ETA mean for the route?
A manager coordinating several workers and deliveries needs route order, current location, and ETA in one place. Splitting those signals across maps, messages, and manual updates makes dispatch harder than it needs to be.
A Next.js application with a manager route planner, worker location flow, Supabase-backed realtime state, and tokenized read-only tracking pages for sharing a specific worker or route.
What the system contains.
Manager dashboard for multiple workers with multiple trips and stops.
Drag-and-drop route planning, stop reordering, save flows, and live ETA recalculation.
Worker-facing location updates designed to keep the manager view current without manual refreshes.
Tokenized public live pages that expose only the worker or route being shared.
Supabase Auth, PostgreSQL, Realtime, and row-level security as the application data layer.
MapLibre rendering with OSRM routing to keep the demo independent from paid map APIs.
System flow.
Technical decisions.
Use an organization-style manager view for multiple workers, trips, and ordered stops instead of treating tracking as a single-driver map.
Use Supabase Realtime so route and location changes can propagate without requiring manual page refreshes.
Use tokenized public tracking routes so a manager can share a read-only view without exposing the full manager workspace.
Use MapLibre + OSRM to preserve the project's no-paid-mapping-cost constraint instead of depending on a proprietary maps bill from day one.
The open mapping stack keeps the demo inexpensive and portable, but it shifts more responsibility onto the application for routing reliability, service availability, and fallback behavior.