Driver App
Driver App gives an authenticated driver a configured mobile workspace for reviewing delivery requests, working through an active delivery, reviewing available order conversations and contact options, and managing driver account information.
This documentation also helps operators understand what the app owns and where configuration, account, operating-system, or provider ownership begins. A visible control shows what the app can present; it does not by itself confirm that an action is eligible, accepted, or completed.
Availability
Use the Driver App supplied for your Ordering project and a driver account that your organization has prepared for it. The exact experience can vary with:
- whether the driver is signed in;
- project configuration and the driver's schedule;
- the type and current state of a delivery request;
- device permissions, platform, connectivity, and app lifecycle; and
- availability of an operating-system or external-provider handoff.
Driver App does not provide public driver signup. Applying to become a driver on a website and assigning work in an operator product are separate workflows. Those workflows do not prove that an account, assignment, or action is ready in Driver App.
Follow the Driver journey
Start with the guide that matches what you can see and the task you need to complete.
| Task | Start here | What the guide helps you determine |
|---|---|---|
| Open the app | Startup and loading | Whether the app is still preparing or has reached the next visible gate |
| Access the driver workspace | Sign in as a driver | Which visible sign-in path applies to the configured app |
| Review available work | Navigate the Driver App | Where to enter the request area before using its task-specific guidance |
| Continue current work | Understand an active delivery | Which information and next action the current delivery state presents |
| Use location context | Use the delivery map | What the in-app map can show and which permission or provider boundary applies |
| Review order communication | View order conversations | How to find available conversations without treating visibility as message delivery |
| Review driver information | View the Driver profile | Which account and availability information is visible |
| Review completed work | Review delivery history | How past-delivery views differ from active work |
The Driver App architecture contract describes the stable public responsibility boundary without exposing private service details or certifying a running backend.
States and boundaries
The app can place a prerequisite ahead of the destination you expected.
| State | What it means | Safe next action |
|---|---|---|
| Startup loading | Session, configuration, permission, notification, schedule, or related readiness work has not settled locally. | Wait for the next visible surface, then use the startup guide if loading does not clear. |
| Tutorial or sign-in | The app has selected a signed-out entry path. | Complete only the visible supported step. |
| Schedule or permission gate | A configured prerequisite is ahead of the authenticated workspace. | Read the matching guide before changing device or account state. |
| Authenticated workspace | The main driver navigation is visible. | Choose the task guide for the relevant order, map, message, or account state. |
| Loading, empty, unavailable, or error content | The current area has not produced usable content. | Do not treat the absence of content as a completed action; follow that area's troubleshooting guidance. |
| External handoff | The operating system or another provider owns the next surface. | Return to Driver App and verify its visible state instead of assuming the handoff succeeded. |
Assignment, order status, location, messaging, contact, notification, session, review, proof, PIN, media, and provider actions have their own eligibility and effect boundaries. Follow the specific guide before taking one of those actions.
Troubleshooting
| What you see | What to check | Safe recovery |
|---|---|---|
| The loading screen does not clear | Connectivity, a pending device prompt, and whether the app was interrupted during startup | Avoid repeatedly reopening the app. Record the platform, app version, time, and visible state without including account, order, message, or location details, then contact your app operator. |
| A different first screen appears | Tutorial, session, schedule, configuration, and permission state can change startup priority. | Use the guide for the screen that is actually visible. Do not bypass a prerequisite through an adjacent product. |
| A task or control is missing | The account, configuration, order type, order state, platform, or permission may not admit it. | Ask the operator responsible for the account or project configuration; visibility in another product is not proof that Driver App should show it. |
| An action was requested but the result is unclear | A request, server decision, follow-on effect, and provider handoff are separate. | Stop before repeating the action and verify the observable Driver App state in the task-specific guide. |
Next steps
If you have just opened the app, continue with Startup and loading. If the authenticated workspace is already visible, choose the task group above that matches the current screen, beginning with Navigate the Driver App when needed.
Related guides: Startup and loading · Sign in as a driver · Navigate the Driver App · Driver App architecture