-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mobile FTUE: Create an Account (meta) #128
Comments
Username infoSpec references:TL;DR
|
We should ask the keyboard not to capitalise the first letter of the username as capital letters are not allowed in usernames and it has been seen in usertesting to trip people up: |
I would like to criticize this part:
Do we only see #126 by clicking edit here? I would argue that #126 should be shown before landing here to inform about (and perhaps encourage) server choice. Is there an overview flow graph somewhere? |
for some extra context, here's the current web account creation (we've aligned quite closely~)
correct, the server selection screen is currently only accessible by tapping
|
Thank you, Adam. I agree it is well aligned with web. |
We want to provide the user with a screen to create an account.
Depending on the server chosen there are different options available to users at the sign up stage. Due to this complication users must select the server they would like to create their account on before moving forwards with the account creation process. This question confuses new users who are not aware of what this means and can lead to serious detractors and big negative impact on our EPU score (we can see this in the difference between iOS and Android scores today where android users are offered this choice first). To minimise the impact of this decision, reduce the stress it creates, and ensure server options are front and centre for all users, this is our chosen design:
If the user chooses to edit the server they are taken to the select server screen #126
When the server is chosen the SSO options may change.
The text was updated successfully, but these errors were encountered: