As a user, I am invited to a site. User opens the link in the browser.

    User reads and wants to subscribe

      2

    User is subscribed, no button is shown on the screen. 
User can unsubscribed from the email (ie: Gmail)

      User check People’s tab

        1

      User clicks follow and is prompted to create an account.

        1

      Create account
      Tiggers when user wants to do certain actions

        Step 1 : User Adds email

      We show from the beginning the steps required

      User should be able to close anytime (add an x top right)

      We facilitate the experience with clear copy text to set up expectations

      Title is centered in the value not in the action (Join the conversation not create an account)

      The CTA is connected to the button (join) so it doesn’t feel disconnected

      “Account creation” is framed as infrastructure, not intent

      4

      Step 2: User adds a secures account

        Don’t be too techical: over-explain cryptography, you lose people. Don’t explain what a passkey is technically, explain what it does for the user.


        If device supports passkeys → show it first + recommended If not → hide passkey option entirely

    1

    Step 3: User adds profile

    User is already joined and has an account - (browser) - Following a user

    After the action that triggered creating an account (ie, follow/comment/bookmark), tool shows how the user is already following and signed in with all the functionalities available (notifications, bookmark, comment...)

    User is already joined and has an account (app) - Following a user

    On app we will show the following people on the left bar.

    Sign in

      User taps "Already have a Seeds account? Sign in" after clicking join button

    After adding email it triggers -> Passkey when applies or password as a fallback

    User selects passkey

      We need confirmation message when it works

      We need error message when something fails

    1

    Authorize screen

      Reframe the wording on this screen to feel safe. Avoid words as "authorize" "Allow access"

      Hide technical details by default, more comprehensive copy and info. Design it to feel safe.

      Don't add too much cognitive load at a moment that should feel like progress.

      1

      This screen just appears when multiple users I guess Eric Vicenti