Understand Customer App entry states
The source-defined public Home surface can present language, Log in, Sign up, and a conditional Guest control to an unauthenticated customer. Each control is an entry or handoff boundary. Its visibility or disappearance does not prove authentication, registration, guest-session settlement, later checkout eligibility, or an order outcome.
:::warning Important limits Required account, connectivity, profile, project, tutorial, or other startup state can supersede public Home. Source inspection does not certify which entry state is deployed for a particular project or build. :::
Keep entry layers separate
| Layer | Observable state | Safe interpretation |
|---|---|---|
| Startup | Another prerequisite or connectivity state appears | Public Home has not become the current entry surface. |
| Public Home | Language and available entry controls are presented | Presentation only; no session is established by visibility. |
| Log-in handoff | The login experience is presented | Navigation occurred; authentication remains owned by Log in. |
| Sign-up handoff | The registration experience is presented | Navigation occurred; account creation remains owned by Sign up. |
| Guest pre-action | Guest is visible | The source-defined conditional control is available; session authority is unchanged. |
| Guest pending or unknown | Guest intent was already submitted but current authoritative session state is absent | Do not infer success or failure from Home closing, navigation, a toast, or loading alone. |
| Authoritative session | Current session state identifies the active guest or registered account | Entry state can be reconciled; later product eligibility remains separate. |
Public Home states
The pinned UI can show translated introductory content and a language control. The complete action group can be absent while shared order or entry state is loading. That presentation does not prove which read or write started.
Guest is conditional. This reference does not promise a configuration value, deployed availability, or checkout support. When the control is absent, use an available registered-account handoff; do not infer a defect or hidden guest capability.
Account handoffs
- Log in can present the login experience. Authentication, errors, session issuance, verification, and return state belong to Log in.
- Sign up can present the registration experience. Account creation, verification, profile completion, and guest conversion belong to Create an account or continue as guest.
- The language control can present account-language settings. Language loading, availability, persistence, and empty/error states belong to Account settings.
An opened destination is evidence of a handoff only. It is not confirmation of the destination's account or session outcome.
Guest is an effect-capable boundary
Selecting Guest can start account/session and local-state work. This page does not provide a Guest procedure and does not use navigation as confirmation.
If Guest intent has already been submitted, classify it as pending until a current authoritative session result is available. If the app cannot establish that result, classify it as unknown. An error can occur after some server or local work, and a changed screen can occur before all session work settles.
Do not submit another Guest intent while the result is pending or unknown. Preserve the current visible state and escalate with only a value-free state class such as “guest entry unresolved.”
States and ownership
| State | What may be visible | Owner and safe boundary |
|---|---|---|
| Startup prerequisite | Verification, profile, connectivity, project, or tutorial surface | Complete only the supported visible prerequisite; startup owner decides the next state. |
| Loading | Home content with entry actions absent | Wait for a settled visible state; loading does not prove a request. |
| Guest absent | Account handoffs without Guest | Use a visible account handoff; project/deployment availability is unverified here. |
| Guest pre-action | Guest visible and idle | No session effect yet from visibility. |
| Guest pending | Existing intent with no authoritative result | No repeat action; keep the outcome pending. |
| Guest unknown | Error, interruption, or conflicting presentation without authoritative session state | Stop; do not infer no effect or session success. |
| Signed-in or guest session | Current authoritative session state is available | Follow the current app state; later address/business/cart/checkout authority remains separate. |
| Offline | Connection state replaces or interrupts entry | Use offline and reconnect guidance; no session result is inferred. |
Privacy and accessibility
Do not place credentials, contact details, guest capabilities, session values, project identifiers, errors, screenshots, or timing in support reports. Use only the visible surface and value-free state class.
Entry controls, loading, errors, focus order, language, large text, keyboard, screen-reader names, and platform Back behavior require current-platform verification. Do not rely on color, disappearance of Home, or a toast as the only state indication.
Troubleshooting by observed state
| Observation | Safe response |
|---|---|
| Expected Home is not visible | Identify the current supported prerequisite; do not bypass it. |
| Entry controls are absent | Keep the state loading or unavailable until the current surface settles. |
| Guest is absent | Use a visible account handoff; do not infer project configuration. |
| Login or sign-up destination appears | Continue in the owning account guide; the handoff is not account success. |
| Guest intent has no authoritative session result | Keep it pending/unknown, do not submit another intent, and escalate value-free context. |
| Session state is current but Home content differs | Transfer to location or business discovery; session and order context are separate. |
Recertification triggers
Recheck this reference when startup priorities, Home entry controls, Guest identity/session behavior, account handoffs, language ownership, project selection, offline handling, session persistence/teardown, navigation, or shared accessibility primitives change.
Related guides: Use the introductory tutorial · Log in · Create an account or continue as guest · Account settings · Choose a delivery location · Browse businesses · Use the app offline and reconnect · Startup and updates