Operational execution interface for provider-employed drivers powering container delivery, collection, and real-time logistics management.
Orders container rentals, tracks driver, receives completion
Central orchestrator, business rules, state machine & sync
Provider operations assigns & dispatches drivers
The Driver App receives assigned tasks from the Supplier Dashboard, provides actual GPS tracking back to the Naqla Platform, and updates order states directly for the customer and admin.
Monitors real-time platform metrics, driver activity, exception escalations, proof validity, and cross-provider compliance.
Replaces manual phone calls and paper receipts with a structured, step-by-step mobile task workflow for container delivery and collection.
Streams real-time physical GPS coordinates to the Naqla backend during active tasks, giving customers accurate ETAs and operational transparency.
Eliminates missed or delayed updates. Every status change immediately syncs across Customer App, Supplier Dashboard, and Admin Dashboard.
Mandates standardized digital signatures, geotagged photo evidence, timestamping, and asset condition notes prior to task closure.
Enforces defined failure reasons (e.g., inaccessible site, customer absent) so provider dispatchers can take immediate operational action.
Full support for Arabic and English languages with flawless RTL/LTR UI layout transitions optimized for multicultural driver fleets.
"Enter through Gate 3. Drop container next to the east construction site tower."
Direct action button allows the driver to report site access issues, unsafe drop-off locations, or wrong pin coordinates immediately to provider operations.
Task lands in driver app inbox
Driver confirms receipt (if configured)
Travel begins; Live GPS turns ON
Truck reaches customer site
Physical placement of container
Photo + Signature captured
Backend updates Active Rental
Task issued at rental end
Driver travels to pick-up site
Driver inspects container asset
Check ID & record damage notes
Loaded photo + confirmation
Rental officially closed
Unlike delivery, collection requires physical asset inspection, verification of serial/container numbers, damage documentation before loading, and official rental closing protocol.
If the container suffers damage or contains unauthorized hazardous waste, driver notes and photos protect the provider and feed into dispute resolution.
Captures Lat/Long + Time
Validates & Filters Payload
Renders Live Truck Location
In rural Saudi industrial areas where standard addresses may be imprecise, the app prioritizes exact GPS pin drop coordinates provided during customer checkout.
Mandatory site drop-off/pickup photograph with watermarked GPS & timestamp.
Digital touch-screen signature captured on site from customer representative.
Server-validated completion timestamp preventing backdated submissions.
Physical verification of container serial number prior to release.
Optional or mandatory structural damage notes captured during collection.
Proof rules are highly configurable by task type, provider organization, or client contract requirements (e.g., photo mandatory, signature optional).
Selecting a failure reason mandates capturing explanatory driver notes, geotagged obstacle photos, and auto-logging exact GPS coordinates.
Drivers can initiate voice phone calls to customers during active tasks only (e.g., clarifying site entry gates or announcing arrival).
Personal driver and customer phone numbers are masked or minimized where feasible to protect user privacy in accordance with Saudi data regulations.
In-app text messaging is NOT assumed for MVP unless explicitly approved during client decision confirmation.
One-touch quick call buttons connect the driver directly to their Provider Operations Dispatcher or Naqla Platform Support.
Toggle instantly between Arabic and English with dynamic LTR/RTL layout reflow.
Set operational status: Available, On Task, Offline, or Suspended.
Manage push notification sound and vibration alert behaviors.
Direct escalation shortcut for app issues, site emergencies, or safety incidents.
Provider dispatches driver
Travel begins; GPS tracking ON
Driver reaches customer site
Unload/load container asset
Photo + signature uploaded
Backend state finalized
| Capability / Feature | MVP Scope | Phase 2 / Future | Separate System | Notes & Guidance |
|---|---|---|---|---|
| Driver Auth & Inbox | MVP | - | - | Secure OTP login, task listing, details view |
| Delivery & Collection Lifecycle | MVP | - | - | Status transitions (En Route, Arrived, Complete) |
| Actual GPS Tracking | MVP | - | - | Actual hardware location updates during active tasks |
| Proof Capture & Failures | MVP | - | - | Photos, signature, timestamp, standardized failures |
| Advanced Driver In-App Chat | - | Phase 2 | - | Controlled calling in MVP; Chat deferred |
| Driver Payroll & HR Management | - | - | Separate | Managed within Provider ERP / HR systems |
The Driver App cannot function independently. Driver creation, truck assignment, and task dispatching originate entirely within the Supplier Dashboard.
All status updates, proof photo uploads, failure reports, and live GPS streams rely on the availability of central Naqla REST and WebSocket APIs.
Navigation launching, address pin resolution, and dynamic ETA calculations require active integration with third-party maps services.
Immediate alert dispatching for new tasks and schedule cancellations depends on Firebase Cloud Messaging (FCM) / Apple Push Notification service (APNs).
| Decision Area | BRD Requirement Details | Client Sign-off Action Needed |
|---|---|---|
| Task Acknowledgement | Will drivers be required to explicitly acknowledge tasks with an auto-reassign timeout? | Confirm timeout duration (e.g., 15 mins) |
| GPS Frequency & Retention | Final update frequency (e.g. 30s vs 60s) and background tracking retention window. | Confirm battery vs accuracy trade-off |
| Proof Rules Matrix | Determining mandatory vs optional status for signature and photo for each provider. | Approve proof rules per service tier |
| Driver-Customer Calling | Selection of phone number masking provider vs direct cellular calling. | Confirm proxy gateway budget & provider |
| In-App Chat Scope | Confirm whether text chat is strictly Phase 2 or required in MVP. | Sign off MVP exclusion |
Selects container size & location pin
Dispatches task in Supplier Dashboard
En route, drop-off, proof captured
Customer uses container for rental period
Pick up proof uploaded, order closed
The Naqla Driver Mobile App provides the critical operational execution layer for provider-employed drivers, ensuring reliable container delivery, actual GPS visibility, and standardized proof of service.
Confirm decision items in Section 28 & 32
Figma clickable prototyping (Arabic & English)
Define REST endpoints & WebSocket payloads
Development estimation & release timeline