In-app help

Help appears only where a card exists for the step you are standing on

The control that opens a help card lives in the wizard header and is bound to the step beneath it. A pair the lookup does not know produces no icon rather than another step's card, and a card that does open is written in your interface language.

Help is attached to the step, not to the screen

The Create flow carries its help in the header of the wizard. The wizard resolves a help key for the step you are on; only when a key exists does it create the handler that opens the card, and the header draws the control only when that handler reached it. The files are apps/jewelry-mobile/src/features/generation/create-flow/create-wizard.tsx and create-flow/wizard-header.tsx:37, read from the app source in August 2026.

The consequence is narrow and worth stating plainly: the presence of the question mark is a statement about the step beneath it. It is not a signal about the health of the app, the state of your connection, or whether the tool you picked is working.

The processing screen supplies the same property on its own (create-flow/processing-screen.tsx:133), so the control there follows the same condition it follows inside the wizard.

What the header shows, state by state

Four states, and what decides each one. These rows describe the control only, not the content of any card.

Where you are	The question mark	What decided it
No tool chosen yet, at the first step	Drawn	The lookup resolves the no-tool state to the tool-selection card
A tool-and-step pair the lookup knows	Drawn	A card is defined for that exact pair
A pair the lookup does not know	Not drawn at all	Help is hidden instead of being resolved to another step's card
The processing screen	Follows the same property	That screen passes the property itself (processing-screen.tsx:133)

A missing icon is a decision, not a failure to load

Each of these is readable in create-flow/help-content.ts and in the two wizard files named above.

The control is absent, not greyed out.: There is no dimmed or unpressable version of the icon to interpret. Where no handler is passed, the header has nothing to draw.
Silence is preferred to a card written for a different step.: A tool-and-step combination the lookup does not recognise returns nothing, which hides the control rather than falling back to the nearest card.
The first step is never left without help.: The state in which no tool has been chosen is mapped directly to the tool-selection card, so that step always carries the control.
The rule says nothing about which tools you can use.: Whether a tool is switched on is resolved from server configuration and cannot be read from the help surface at all.

Written in the source, absent from the experience

These are recorded so that nobody spends time looking for them. None of them is a feature, and none is offered here as something to open.

Two help cards exist in the source, one for the result screen's before-and-after view and one for the library picker, and no step resolves to them; the sheet is not rendered on those screens. What is missing is the card, not the screen.
The help card layout includes a privacy row. No help card fills it, so no privacy line appears on this surface at any step.
That observation is confined to the Create flow's help cards. It says nothing about text anywhere else in the app.
Which tools are enabled is not readable here; that is resolved from server configuration.
The advice inside any individual card is not reproduced on this page. This page describes where help appears and where it does not.

Before you report the help icon as broken

Five checks, in the order that separates a defined absence from a real defect.

Write down the exact tool and the exact step you were on; the pairing is per tool and per step, not per screen.
Check whether a tool had been chosen at all, because the state before that choice always carries a card.
Confirm you were looking at the wizard header rather than at the body of the step.
Note your interface language separately; a card is never shown half-translated, so a language question and a missing icon are two different reports.
Check whether the control returns when you move back a step, since the pairing is evaluated for each step separately.

Questions this page leaves open

Photography technique is not covered here; the guides carry that. Which tools are currently available is resolved from server configuration and cannot be read from the help surface. What the waiting screen promises while a generation runs has its own page and is not restated here.

Everything above was read from the Jewelry AI mobile app source in August 2026, at the files named in the text: create-flow/create-wizard.tsx, create-flow/wizard-header.tsx:37, create-flow/processing-screen.tsx:133, create-flow/help-content.ts and src/i18n/translate.ts.

Questions

Why does the question mark disappear on some steps?

Because a single lookup maps a tool-and-step pair to a help card, and a pair it does not recognise returns nothing. The wizard then passes no open handler, and the header draws no control (create-flow/help-content.ts; create-flow/create-wizard.tsx).

Is the icon disabled, or is it missing?

Missing. There is no dimmed or unpressable state to press; where no handler exists, the header has nothing to draw (create-flow/wizard-header.tsx:37).

Will the help card be in my language?

Every help card has an entry in every interface language, and there is no runtime fallback to English: a missing key fails at build time instead of showing a partly translated card (src/i18n/translate.ts). This covers key completeness only, not translation quality or approval.

Does a help card tell me what happens to my photograph?

The card layout has a privacy row and no help card fills it, so no such line appears on this surface at any step. That statement covers the Create flow's help cards only and says nothing about text elsewhere in the app.