Tarq Logistics
Driver app and dispatch console for a 120-vehicle fleet, built to keep working through the dead zones on the Yamuna Expressway.
120
Vehicles
14
Weeks to launch
72 hrs
Offline queue
2
Platforms
DL-01-AB-4412
last sync 3m ago · queued 2
The problem
Dispatch ran on phone calls. Drivers lost signal for long stretches, so proof-of-delivery photos failed to upload and were re-taken at the depot hours later — or not at all.
The solution
An offline-first driver app that queues every action locally and reconciles when signal returns, paired with a dispatch console showing each vehicle's last known state and how stale it is.
What we built
- Mobile
- React Native driver app with a local queue and conflict-safe sync
- Web
- Dispatch console with live vehicle state and staleness indicators
- Backend
- Idempotent ingest so a replayed queue never double-counts a delivery
- Integrations
- SMS fallback for drivers without a working data connection
Tell us what is held together by a spreadsheet.
One call, a written scope, a fixed price. If we are not the right studio for it, we will say so — usually with a pointer to who is.
- 24h
- Reply to every enquiry
- 48h
- Written scope after the call
- ₹0
- Cost of the first conversation