1. Subscribe

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

1.2. User reads and wants to subscribe. A window opens to add email and an option to join site instead.

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

2. Follow a member of a site

2.1 User check People’s tab in the site

2.2. User sees member's detail with different areas: Bio, Activity, Subscribed sites..., Link to website (if there is)
If user is interested can follow this member. It will be prompted to create an account.

2.3. User sees his own profile

3. Create account

Tiggers when user wants to do certain actions (comment, follow, bookmark a document)

3.1. Step 1 : User Adds email

We show from the beginning the steps required

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

-> Copy of the paragraph will changed depending of the action that prompted created an account flow (comment. follow or bookmark)

3.2. User has to click email link to be verified

3.3. Email is verified

3.4. 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. 

By now we just add the option to secure with passkey until we have the password flow ready and considering all edge cases hm://z6MkgisVMELvqnsCo3dYmtVpy8PiqPGMVwfAyBWFn84vebq4 hm://z6MkrbYsRzKb1VABdvhsDSAk6JK8fAszKsyHhcaZigYeWCou .

I propose to create a link to a Seed doc. "Not familar with passkey? Learn how it works" and explain basic about passkeys to learn more about it.

3.5. User adds profile

4. User has an account

4.1 When account creation is successful user goes back to the action that triggered account creation -> Follow, Comment or Bookmark).

From 3.5 goes into this screen when the action was comment👇

New comment is marked in green

From 3.5 goes into this screen when the action was follow or bookmark👇

4.2. User has joined the site, is subscribed and has all the functionalities available.

Browser

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

5. Sign in

5.1 In step 3.1 user taps "Already have a Seeds account? Sign in"

Sign in first step, we welcome back the user

5.1 After adding email it triggers -> Passkey

5.2 Passkey steps happen in the device

5.3. 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.

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

5.4. When "Vault is locked"
Avoid very technical words that feel dangerours (Lock, Authenticate,,)

6. Account settings

6.1 User clicks the profile icon and goes to this screen

6.2 User clicks "manage account" - A new screen opens (open blank)

6.2.1.User can edit Name and avatar directly and save if he does edit

6.3 User clicks "Security and Sign in"

6.4 User clicks "Notifications"

7. Site options

When pressing the 3 dots options in app user can Leave the site, which means unjoin and unsubscribe.

Can also:

Manage Site notifications

Invite someone to join (by now just a link sharing flow)

See all documents (in the future)

8. Join versus logged in

Seeing the behaviour in action we agreed with Horacio that the "join" button should not be mistaken by the account button.

There are 3 options here:
1. User is not logged in and haven't joined the site

2. User is logged in but haven't joined the site

3. User is logged in and have joined the site