Skip to guide content
Random Addingby Melirate

Guest profile

Understand guest data and practice scores

See what this guest preview keeps on the device, how room results are labeled, and where learning-evidence claims stop.

Available locallyJourney guide

Before you start

  • Use guest play. The current hosted preview remains unconfigured for member access; member code prepared locally is pending activation.

Steps

  1. Use a nickname only

    The first Play now or Challenge friends action asks for a nickname. Random Adding does not ask for an email or password. Basic filtering is not a child-safety guarantee.

    Open the Guest profile: first nickname guide

  2. Understand browser storage

    Nickname, settings, and solo summary records are stored per browser profile when storage works. Clearing storage, private browsing, or another device may create a new guest identity; there is no cross-device recovery.

    Open the Guest profile: returning identity guide

  3. Check the result label

    Solo guest results say Saved on this device only after browser storage confirms a write. Group results remain guest room results; local accepted room status is not a Melirate member receipt or learning evidence.

    Open the Results: metrics and local save guide

  4. Keep guest and member records separate

    Guest and group scores are never silently imported into a learner record. In an enabled member flow, verified players and guardians with practice permission can sync new answers to Melirate Activity. Earlier practice saves are summary-only history, separate from new Activity answers. Eligible new solo facts contribute to skill predictions.

    Open the Open Challenge: result sync states guide

What to expect

  • The result screen reports local save failure instead of showing a false save success.
  • No guest score is silently imported as member evidence.

Other paths

Visual guide

Recorded walkthrough

Walkthrough recording · 12 sec

These are silent local synthetic preview captures. Account clips and screenshots show the unconfigured guest preview, not the locally prepared member flow. Some demos use 5-, 15-, or 20-second timers; private invitation details are hidden. If playback is unavailable, use the captions when present or read the full transcript below.

Read the full recording transcript

Create a synthetic guest profile through the real nickname sheet.

The result says whether it was saved on this device and clearly states guest practice is not verified learning evidence.

After a reload, the guest nickname remains on this browser. The page does not offer account deletion or claim hosted storage.

The sign-in information confirms there is no configured account connection here; guest play remains local.

Annotated screens

Each numbered note names the control or state marked on the screen.

Actual first-use guest nickname sheet: name and scores stay in this browser; it asks for no email or password.View full-size original annotated screen (new tab)
Annotated Random Adding screen.

What the numbered markers show

Actual nickname validation: a 30-character synthetic name is rejected with an inline 24-character limit message.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual first-use guest sheet at 320 × 568 CSS pixels; nickname field and continue action are visible in the mobile viewport.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual returning synthetic guest profile: the same browser opens the edit sheet with its saved nickname prefilled.View full-size original annotated screen (new tab)
Annotated Random Adding screen.

What the numbered markers show

Actual setup after editing the synthetic guest nickname; the updated name is shown in the app header and the device-local profile remains.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual completed solo result with score, accuracy, longest streak, best score, Flawless badge, device-save status, and guest-practice boundary.View full-size original annotated screen (new tab)
Annotated Random Adding screen.

What the numbered markers show

Actual replay result comparing this new round with the previous round that was just completed in this same synthetic browser.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

Actual honest result state when storage is blocked: the synthetic guest can play, but the round could not be saved.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

The room service accepted this synthetic score and shows a rank. Local review does not claim learning evidence.View full-size original annotated screen (new tab)
Annotated Random Adding screen.

What the numbered markers show

While offline, the actual local score remains visible with a Retry sync control and no invented rank.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

After reconnect, retry obtains an actual accepted room receipt for the same local score.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show

The room service really rejected an attempt after the host ended the room; the local result stays visible without a placement.View full-size original annotated screen (new tab)
Additional annotated screen state.

What the numbered markers show