01 / Logistics infrastructure
Deployed app2026
RouteFlow
Live worker tracking, multi-stop routing, ETA recalculation, and shareable public tracking views.
LIVE SYSTEM / ROUTE NETWORKPUBLIC VIEW + MANAGER VIEW
REALTIME
ETA
Problem
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.
System
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.
Next.jsTypeScriptSupabasePostgreSQLRealtimeMapLibreOSRM
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.
Tradeoff
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.