Case study · 2024
Smart Transport
Real-time fleet management with dynamic dispatch: one job lifecycle shared by a dispatcher's console and a driver's phone, updated as events while the trip runs.
- Runs on
- WebiOSAndroid
- Built with
- MUI · React · React Native
- Role
- Full stack. Designed the job lifecycle with the UX lead, then built the admin console, the driver app, and the backend they share.
The problem
A haul has two people looking at it. The dispatcher sees every truck at once and changes plans as the day moves. The driver sees one job and is on the road. When their pictures disagree, a truck goes to the wrong gate or waits for a load that was reassigned.
The two screens had to tell the same story about the same job, at the same moment, while the job itself kept changing.
Constraints
- Plans change mid-trip. Dispatch is dynamic, not a morning schedule.
- Dispatchers watch many trucks at once in dense tables and a map.
- Drivers need the next step, not the whole board, on a phone in a cab.
One lifecycle
Decisions
One job lifecycle, two clients
The console and the driver app share one set of job states, from assigned through loaded to delivered. Each client draws them for its own person, but neither invents a status the other does not know.
Trade-off. A new state is a change to both clients and the backend at once. That is slower to add and impossible to drift.
Status travels as events
Position and status changes are pushed as events, so the dispatcher's map and table move while the trip runs. A reassignment reaches the driver as a push notification instead of waiting for a refresh.
Ready-made where it is standard
MUI covered the dense tables, date pickers, and dialogs, so the effort went into the map and the job flow, where the product is specific.
Full stack, one owner
I designed the job lifecycle with the UX lead, then built the admin console, the driver app in React Native, and the backend they share.
Result
- Part of the transport management system used in daily fleet operations.
- One of 8+ web and mobile apps we shipped to 5,000+ active users.
Read deeper
- The frontend is a control plane
Operator interfaces work when navigation, state, and actions follow the system a person is responsible for. A dashboard that only reports on that system is a different product.
- Offline-first is a product decision
A local database and a retry queue are implementation. The product decision is which actions may succeed before the server agrees, and what a person is owed when the server later disagrees.
The screens are rebuilt in React with sample data. Open them from the work section.
Next: Task Manager →