✅ As a new User, I create a Hypermedia web account from the browser with passkeys

✅ As a new User, I create a Hypermedia web account from the browser with passkeys


    Behavior from source: From Join or an attempted message, introduce the originating site and Hypermedia, open the Hypermedia identity flow, validate email with a four-digit code, create a native passkey, and complete a named profile. Return to the originating site as a joined member. The source also embeds a separate implementation review log with requested corrections.

    Original source · exact version bafyreif7o5a3gsrsvxh3rajwtxvv75xbb7okmy7i26xkxdjhxshdv4eani

    Reviewed migration decision · Journey map · local task ID ut-ed6bb916bbdfe380.

    Confidence: high; review status: needs-review. Similar source records are not merged. Source status icon is not a committed release or current product state.

Source acceptance and behavior

    The entry remains in the originating site UI, names the site first and briefly explains Hypermedia before asking for action.

    Offer Create my identity, I already have a Seed identity, and I have an identity from another site; closing the dialog lets the visitor keep reading.

    Create my identity opens a clearly branded Hypermedia environment in a new window; use Identity rather than Vault and show Email, Verify, Passkey, Profile progress.

    Validate email format before submission and keep Send code disabled until valid; display terms/privacy links below it (pages still to be created).

    Send a four-digit email code; show four input boxes and the email address; correct code advances automatically.

    Wrong code displays a friendly inline error without lockout on the first attempt; resend activates after 60 seconds and shows remaining time; expired codes can be replaced without losing email.

    An email already associated with an identity leads to sign-in with Welcome back instead of creating a duplicate account.

    Explain passkeys in plain language and provide a What is a passkey? help link (page still to be created).

    Create a passkey with native biometrics or PIN, then automatically advance to Profile; mobile devices without biometrics use PIN.

    Cancelled or failed passkey creation permits retry. Unsupported devices should receive a fallback, but the source marks password fallback as future work.

    Require a display name; profile photo is optional and can be added later in Account Settings.

    Show validation for a missing name or invalid/oversized photo, with accepted formats and size limit; this source does not give a numeric limit.

    Browser Back returns to the previous step without losing progress.

    Start participating returns the user to the originating site as a joined member.

    Show a joining toast for five seconds with copy specific to Join versus posting a message.

Full original readable source and block backlinks

    Paragraph a) User click Join source block

    Paragraph b) User creates a new message and join flow is prompt source block

    Heading Acceptance Criteria source block

    Paragraph Screen 1 — Entry (Ethosfera) source block

    Paragraph The entry screen remains within the Ethosfera site UI. source block

    Paragraph The screen acknowledges Ethosfera by name first, then introduces Hypermedia as the underlying identity layer (in one or two plain sentences, without a lecture). source block

    Paragraph The copy answers the implicit question "what is Hypermedia?" before asking the user to do anything. source block

    Paragraph Three paths are presented: Create my identity, I already have a Seed identity, I have an identity from another site. source block

    Paragraph Keep reading option is available by closing the dialog. source block

    Paragraph Clicking "Create my identity" transitions the user into the Seed Hypermedia environment in a new window without feeling like an abrupt jump. source block

    Paragraph Screen 2 — Email (Hypermedia) source block

    Paragraph The user is now inside the Hypermedia environment, clearly branded with its own UI and background. source block

    Paragraph No new concepts are introduced here. We don't use the term "Vault" but "Identity", easier to understand for the user. source block

    Paragraph A progress stepper shows 4 steps: Email, Verify, Passkey, Profile. source block

    Paragraph Email field validates correct format before submission. source block

    Paragraph Terms of service and Privacy policy links appear below the Send code button (we need to create this page). source block

    Paragraph Submitting triggers a 4-digit verification code to the provided address. source block

    Paragraph The button is disable until the email added is a correct source block

    Paragraph Screen 3 — Verify Email source block

    Paragraph Four individual input boxes are shown for the verification code source block

    Paragraph The email address is displayed so the user can confirm it source block

    Paragraph A Resend code link is available without refreshing the page with the time left source block

    Paragraph Correct code automatically advances to the next step source block

    Paragraph Incorrect code shows a clear, non-technical error message in red bellow the inputs: "Wrong code. Try again." source block

    Paragraph Screen 4 — Passkey source block

    Paragraph The screen explains passkey in plain, friendly language source block

    Paragraph A "What is a passkey?" link is available for unfamiliar users and opens a document in Hypermedia website (We need to create this page, let's copy paste some article) source block

    Paragraph Passkey creation uses the device's native biometric or PIN prompt source block

    Paragraph On success the user advances automatically to Profile source block

    Paragraph We need to review potential errors here to create copy source block

    Paragraph Screen 5 — Profile source block

    Paragraph User can enter a display name (required) source block

    Paragraph User can optionally upload a profile photo source block

    Paragraph Photo upload can be skipped or completed later in Account Settings source block

    Paragraph Screen 7 — Done source block

    Paragraph Confirmation screen shows a toast with joining confirmation that disappears after 5 seconds. Message changes depending of where the user comes from: a) Join b) posting a message source block

    Heading Basic Flow source block

    Paragraph User lands on Ethosfera and sees the join nudge within the site source block

    Paragraph User clicks "Create my identity" - transitions to Seed Hypermedia source block

    Paragraph User enters email and clicks Send code source block

    Paragraph User enters 4-digit code from inbox — advances automatically on success source block

    Paragraph User creates a passkey using device biometrics or PIN source block

    Paragraph User enters display name and optionally uploads a photo source block

    Paragraph User clicks "Start participating" and lands back on the site as a joined member source block

    Paragraph Joined confirmation is displayed source block

    Heading Edge Cases source block

    Paragraph Email source block

    Paragraph ⚠️ If the email format is invalid, an error appears in red bellow the input: "That doesn't look like a valid email" source block

    Paragraph ⚠️Verification email not received → Resend code link activates after 60 seconds source block

    Paragraph ⚠️ Incorrect verification code entered → friendly error, no lockout on first attempt source block

    Paragraph ⚠️ Verification code expires → option to request a new code without losing email entry source block

    Paragraph ⚠️ If the email is already linked to an existing Seed identity, the form does not create a new account, instead it prompts the user to sign in, with a text: "Welcome back" source block

    Paragraph Passkey source block

    Paragraph ⚠️ Device does not support passkeys → fallback method offered, user not blocked (password needs to be developed later) source block

    Paragraph ⚠️User cancels the biometric prompt → returns to passkey screen, can retry source block

    Paragraph ⚠️ Passkey creation fails due to device error → retry option shown source block

    Paragraph Clear error messages: avoid: "Failed to fletched" "Invalid Handoff token" source block

    Paragraph Profile source block

    Paragraph ⚠️ User submits without a display name → validation error, photo remains optional source block

    Paragraph ⚠️ Unsupported image format or file too large → clear error with accepted formats and size limit source block

    Paragraph Navigation source block

    Paragraph ⚠️Browser back button mid-flow → returns to previous step without losing progress source block

    Paragraph ⚠️Mobile device with no biometric sensor → passkey falls back to device PIN source block

    Paragraph ⚠️ User tries to create second identity with same email → redirected to sign-in, duplicate prevented source block

    Heading Implementation Review Log source block

Do you like what you are reading? Subscribe to receive updates.

Unsubscribe anytime

Comments