Create account and sign in qa-review

In this document, we present existing current flows for creating an account and signing in with your account.

Create an account

Step 1 - arrive to a community

Step 2 - join and create an account

Step 3 - start email validation

Step 4 - validate your email

Step 5 - use a passkey

Step 6 - add a Passkey

Step 7 - create your profile

Step 8 - join the new community

Step 1:
- Flow Ok.
- Optimization: we need to give better reasons to join because right now nobody is joining.
Step 2:
- Flow Ok.
- Fine. Maybe too wordy IMO (GABO)
Step 3:
- There was a weird flash when the page loaded. Please, let's fix it.
- I get two emails
Step 4:
- I have already seen many users getting lost with this page. Now I understand why is necessary to have the short code and let the user find the page with Step 5.
- At least, is it possible to continue from this page to Step 5? but I don't think the current set up is working.
Step 5.
- I had to refresh the page on step 5 to move on.
- I don't know what is the solution, or if we just need to keep it this way, but people don't understand "Use Passkey" and they drop.
Step 6:
- out of our control.
Step 7:
- What if we merge Steps 5 and 7?
Step 8:
- As you can see on the screen it took me to the account instead of back to the Site.

The user is already a member and wants to join again:

Step 1 - land to site

Step 2 - sign in into the community

Step 3 - use your passkey

Step 4 - confirma and join?

Step 5 - confirmation that you have join

Step 6 - read your notifications

Step 1:
- Step one we are missing the avatar close to the Join button.
Step 2:
- Users don't understand why are they joining again if they have already joined.
Step 3:
- improve the copy.
Step 4:
- is not necessary if there is only one account.
Step 5:
- Why it is congratulating to become a member if I am already a member?
Step 6:
- Should the bottom left buttons be at the top left?
- We are missing the new feed icon.

Desktop flow is the same as the web, except for the screen where the user gets to decide if using a local vault only:

Step 1 - create an account

Step 2 - chose your vault

Step 3 - creating the account and the vault

Initial Sketch

Step 1:

Step 2:

The happy and primary path is creating a remote vault. We add a secondary option: I don't want a vault server running in the cloud.

The same as create an account. Same flow than the web, but we need to design this page

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

Unsubscribe anytime