Open Driver App and reach sign in
When the reviewed Driver App reaches its signed-out Home screen, it shows a welcome surface with a Login control. Selecting Login asks the local navigator to open the registered sign-in screen.
This reference starts only from a visible signed-out Home. It does not guarantee that a clean launch reaches Home, that Login opens the next screen, or that sign-in succeeds.
Availability
Signed-out Home can be selected after startup loading settles, no session is admitted, and the configured tutorial does not take priority. The tutorial's clean first-launch path remains blocked by a permission-loading/setup contradiction, so startup can remain ahead of Home.
This Driver App configuration uses its assigned Ordering project. Signed-out Home does not show a project-selection field. If your app shows a project selector, confirm that version's configuration before following these steps.
State and result matrix
| Starting state | Visible result | Supported next step | Limit |
|---|---|---|---|
| Startup loading | Loading view | Wait for a visible startup result. | Loading does not prove a service or permission result. |
| Tutorial visible | Introductory slides | Follow the tutorial guide only while it is visible. | Tutorial completion and clean reachability are not guaranteed. |
| Signed-out Home | Welcome copy and Login | Select Login once. | Home visibility does not prove account or service availability. |
| Login visible | Configured sign-in form | Use the sign-in guide. | Navigation is not authentication. |
| Forgot visible | Password-recovery form | Use the password-recovery guide. | The request and its result are separate. |
| Signup page found in source or another product | No registered Driver App destination from this flow | Drivers register through the site's driver signup form when the project has it enabled; see Apply as a business owner or driver. Driver App itself is used to sign in. | Source presence does not make a signup screen reachable inside Driver App. |
| Generic network-error or not-found page found in source | No registered Driver App destination | Use the error state on the screen that owns the task. | These wrappers are not supported public routes. |
The signed-out Root stack registers Home, Login, and Forgot. Login and Forgot are navigation destinations; Signup and generic error wrappers are not.
Effects and boundaries
| Control or boundary | Client intent | What remains unproven |
|---|---|---|
| Open Driver App | Start the native/client startup sequence. | Home reachability, session result, permission readiness, or backend availability |
| Login on Home | Navigate locally to Login. | That Login rendered, credentials are accepted, or a session exists |
| Password-recovery entry on Login | Navigate locally to Forgot when the configured sign-in form exposes it. | That recovery is available, requested, sent, or completed |
| Back navigation | Return within the active signed-out stack when the visible screen provides that control. | Cancellation or reversal of an earlier request |
| Adjacent website application | Apply through the site's driver signup form when the project has it enabled. | Approval timing and whether the resulting account is enabled to receive orders |
| Unreviewed link or dormant page | None supported. | Route registration, authorization, or safe destination |
Signed-out Home in this configuration does not need an API request to render or to request local navigation to Login. Surrounding startup, language, configuration, session, notification, permission, and provider work is handled separately.
Platform and layout variations
- iOS and Android use different keyboard and safe-area behavior on signed-out forms.
- Screen size, orientation, language, and theme can change layout and labels.
- The reviewed Home uses a fixed project configuration. Do not document or expose an internal project value.
- Driver App has no reviewed inbound deep-link mapping. Opening an external URL is not a supported shortcut to Home, Login, or Forgot.
Troubleshooting
| What you see | Likely boundary | Safe recovery |
|---|---|---|
| Loading instead of Home | Startup or permission readiness still owns the root. | Use Startup and loading; do not clear storage or change permissions to force Home. |
| Tutorial instead of Home | The signed-out tutorial branch has priority. | Use the tutorial guide if it is visible; do not assume completion will persist. |
| Login does not change the screen | Local navigation did not produce the expected visible result. | Select it only once, record the platform/app version and visible state without account data, and contact the app operator. |
| Forgot is not available from Login | The configured sign-in option can change whether recovery entry is exposed. | Use the sign-in-options or recovery guide; do not open a private route directly. |
| A project field appears | The build uses a different signed-out configuration branch. | Stop and ask the app/configuration owner to confirm the supported build. |
| A generic network-error or not-found page appears through an unreviewed path | The route is not part of the reviewed Driver App navigation. | Return to the supported visible flow and report the route class without sharing link parameters. |
Related guides: Driver App overview · Startup and loading · First-run tutorial · Sign in as a driver · Sign-in options · Reset a password