Navigate the Driver App
After Driver App admits the authenticated workspace, it opens on Orders and provides tabs for Map view, Messages, and Profile. Use these tabs to choose an area before following the guide for a specific delivery, map, conversation, or account task.
A visible tab or screen confirms only the current app location. It does not confirm that its data is current, that an action is eligible, or that a server, realtime, location, notification, or provider effect succeeded.
Availability
The main navigation is available after the app has restored a signed-in driver session and cleared the current startup prerequisites. A configured schedule gate can appear before the tabs. Device permission state changes whether Map view shows the map or permission guidance.
Tab content can also vary with project configuration, account state, connectivity, platform, app lifecycle, and availability of the owning service or provider.
Open this capability
- Open Driver App and wait for startup to settle.
- Sign in through the supported Driver App flow if a signed-out screen appears.
- Complete only the visible schedule or device prerequisite that you understand.
- When the tab bar appears, select the area that matches your task.
If a detail, chat, or session screen is already open, use its visible back control to return to the previous authenticated screen. The permission surface has no visible back control: switch tabs, or let the app return after its local gate changes. Do not use an adjacent product or an unreviewed link to bypass a Driver App prerequisite.
What drivers can understand
| Tab | What it opens | Important boundary |
|---|---|---|
| Orders | The starting area for available and current delivery work | A card or control does not prove assignment, eligibility, acceptance, or status change. |
| Map view | The in-app delivery map when the required local permission state is available | Otherwise the app shows permission guidance; a permission request is not a grant or location update. |
| Messages | The available order-conversation list | Visibility does not prove authorization to send, message delivery, or a read receipt. |
| Profile | Driver account, availability, schedule, session, language, sign-out, and related account entry points that configuration admits | Profile visibility does not prove that an account mutation or session action succeeded. |
Task screens open above the tabs in the authenticated navigation stack. These can include delivery details, logistics details, an assignment form, order chat, permission guidance, and sessions. The task-specific screen owns its inputs, controls, loading, validation, error, and result states.
States and variations
| Visible state | What it means | Next step |
|---|---|---|
| Startup loading | The app has not admitted the authenticated navigation yet. | Use Startup and loading. |
| Schedule prerequisite | The configured client schedule gate has priority over the tabs. | Review the visible schedule requirement before continuing. |
| Orders selected | The default authenticated tab is active. | Review the visible loading, populated, empty, unavailable, or error state before opening a request. |
| Map view selected with permission | The app has admitted the map from its current local permission state. | Use Delivery map; map visibility is not location-effect proof. |
| Map view selected without permission | The permission-specific substitute is visible. | Use Location permissions. |
| Messages selected | The conversation area is active. | Review the visible list; use Order chat after opening a conversation. |
| Profile selected | The account area is active. | Review the visible account sections before choosing a profile or session task. |
| Detail screen above tabs | A registered authenticated task route is active. | Complete or leave that screen using its own guide; returning does not prove an unfinished action was canceled. |
| Realtime or connectivity state changed | Content can become stale, unavailable, loading, or updated independently of navigation. | Verify the owning screen state before taking or repeating an action. |
The tab bar layout can differ between iOS, Android, phones, and tablets, but the reviewed tab order and ownership remain the same. Profile content is remounted after leaving and returning to that tab, so its loading state can appear again.
Troubleshooting
| What you see | What to check | Safe recovery |
|---|---|---|
| The tabs do not appear | Startup, session, or schedule state still owns the screen. | Follow the guide for the visible prerequisite instead of forcing navigation. |
| Map view shows permission guidance | The current local permission result does not admit the map. | Review the permission guide; do not infer the effective permission from a prior prompt. |
| A tab is visible but empty or loading | Navigation mounted before the owning data state became usable. | Wait for a visible result or error and use that area's guide. Do not repeat a mutation. |
| A detail screen opens unexpectedly | A registered in-app or notification transition selected it. | Verify the visible order/detail context without sharing identifiers, then use the detail guide or return once. |
| Content changes after reconnecting or returning to the app | Reads, realtime, lifecycle, and navigation update independently. | Recheck the current screen state; do not treat the update as proof that an earlier action completed. |
| The selected tab loses prior local state | Some screens can remount on tab changes. | Re-enter the task from the current visible state instead of assuming prior input was saved. |
Related guides: Driver App overview · Startup and loading · Delivery map · Location permissions · Order chat · Authenticated bootstrap