Understand introductory tutorial states
The pinned source defines a conditional, signed-out introductory tutorial with six orientation topics. Its pinned packaged setting is off. That source state does not establish whether another build presents the tutorial or how an installed app behaves.
:::warning Source-level reference This page describes source-defined presentation and blocked outcome states. It does not provide first-launch, completion, relaunch, persistence, or customer- support procedures for an enabled variant. :::
Availability boundary
The tutorial route is conditional on startup, session, and locally read state. It has no source-defined menu or app-link entry. Higher-priority account or startup gates can supersede it.
| Source state | Safe interpretation |
|---|---|
| Packaged setting off | The pinned source does not select the tutorial through that setting. |
| Conditional setting on | The tutorial can become one candidate signed-out startup route; actual presentation remains unverified. |
| Signed-in session | The tutorial is not the source-defined signed-in startup route. |
| Startup read pending | Navigation creation can wait; no tutorial state is yet authoritative. |
| Prior completion state read | Source can suppress the route; durability and later behavior are not certified. |
| Read failure or ambiguous value | Source behavior is not a customer recovery contract. |
Source-defined slide topics
The six local slide records introduce:
- Customer identity choices.
- Business discovery.
- Menu and business information.
- Product discovery.
- Checkout concepts.
- Order-completion concepts.
The slides are orientation content only. They do not create an account, select a location or business, add a product, authorize payment, place an order, or prove any downstream capability.
Controls are presentation, not outcomes
The source defines labels for Next, Skip, progress dots, and a final Let's start! control. It does not wire the visible Back renderer into the slider. Translation, dependency behavior, layout, and platform state can change what is presented.
| Control/state | Source-level boundary |
|---|---|
| First slide | Skip can be source-visible; no result is promised. |
| Middle slide | Source state can hide Skip after the first index. |
| Next, dot, or swipe | The slider dependency owns movement; no runtime result is certified here. |
| Final control | Source dispatches local completion work and then changes tutorial state; visible departure is not persistence proof. |
| Missing callback or rejected local work | Outcome can be partial or unknown; public recovery is not defined. |
Completion states remain blocked
The source dispatches local completion storage without awaiting durable settlement before changing tutorial state. Therefore these are separate:
- final-control intent;
- immediate tutorial visibility;
- local write settlement;
- later startup read; and
- the next visible destination.
No one visible state proves the others. If an enabled variant produces an unexpected outcome, keep completion unknown and use only an already-present, verified in-app return control. Do not infer persistence or repeat the final effect from this reference.
Variations and accessibility
Translated text, bundled images, screen dimensions, orientation, platform, font scale, and slider dependency behavior can affect the presentation. The source limits title and description lines and does not provide complete semantic labels, roles, hints, or image descriptions.
An enabled variant requires separate current-platform evidence before claims about focus, control names, slide announcements, large-text reflow, keyboard or switch access, reduced motion, Back behavior, or iOS/Android parity.
Safe troubleshooting boundaries
| Observation | Safe disposition |
|---|---|
| Tutorial absent | Treat the source-defined variant as unavailable; use the current supported entry surface. |
| Control differs from the source label | Keep interaction behavior unverified and transfer to the implementation owner. |
| Final action changes the screen | Navigation changed; completion and persistence remain unknown. |
| Tutorial appears in an unexpected state | Stop; do not repeat completion or manipulate local storage. |
| Text or controls are inaccessible | Record only slide/state/platform class and transfer to accessibility ownership. |
Support reports must not contain account, session, device, project, local- storage, provider, configuration, or screenshot data. Use only value-free state classes.
Recertification triggers
Recheck this reference when tutorial gating, slide data, slider dependency, translation, startup ordering, local completion handling, navigation callbacks, platform layout, or shared accessibility primitives change.
Related guides: Understand Customer App entry states · Choose a delivery location · Browse businesses · Understand platform and accessibility differences