Skip to content
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

Clarify first-time user signup flow [?] #573

Closed
jlgoldman opened this issue Apr 2, 2018 · 8 comments
Closed

Clarify first-time user signup flow [?] #573

jlgoldman opened this issue Apr 2, 2018 · 8 comments

Comments

@jlgoldman
Copy link

jlgoldman commented Apr 2, 2018

Acceptance Criteria

[stub]

Context

Comment from @jlgoldman :

If I've never used Affinity and I want to join a subgroup, I'm asked to enter my email, then I get sent to a login page. If I'm a first-time user, I'll need to sign up first, but I'll never see the tiny "Sign up" link at the very bottom. I suspect for most users in this case this will wind up just being a dead-end. If you know I'm new to Affinity, just tell me to do the right thing and create an account.

@aguestuser
Copy link
Contributor

"I'm asked to enter my email, then I get sent to a login page."

^-- i'm confused. if i visit a page like groups/5/signup_forms/2/signups/new, after completing the form, i get logged in automatically and sent to my group's dashboard. do you get sent somewhere else?

assuming for now, that the second issue you raised is the main "issue" here, i completely agree. the "sign up" below is too small:

signup-too-small

we have a (stub) issue for fixing this: #505

i'm hearing that playing that card is "must-have" for hard launch. is it also "must have" for soft launch?

@aguestuser
Copy link
Contributor

ps: @tyesha this might be a great spot for some UX input! (as i'm pretty sure that the signup v. login issue is a settle problem among actual UX people. ;))

for reference, i think spotify handles this fairly well with their user flow, which starts by foregrounding the choice between signing up or logging in then proceeds to show only the details relevant to the path people have chosen (so that people don't hit a "dead end" as described below.) absent any input, i'd probably try to make something like this:

spotify-signup-login-choice

@jlgoldman , @mattewing @Matt-Holland : thoughts/input welcome!

(probably not playing this this week, so we can circle up to discuss optimal UX before i do.)

@aguestuser aguestuser changed the title New user signing up for subgroup has confusing flow Clarify first-time user signup flow Apr 2, 2018
@aguestuser aguestuser changed the title Clarify first-time user signup flow Clarify first-time user signup flow [?] Apr 2, 2018
@jlgoldman
Copy link
Author

Try this in an Incognito to simulate the experience of a first-time user. I get redirected to the Sign In page after entering my name, email, and zip.

This is presumably what every group member is going to see when invited by the group creator. So it should be very clear that if this is the first time they've ever seen Affinity, they need to create an account using either social login or a password.

At this point, you know for sure that they're new to Affinity, because you collected their email on the previous page. So the previous page should be a fork for logged-out users: if Affinity recognizes their email, send them to a page that says "Welcome back, please sign in". If Affinity does not recognize their email, send them to a page that introduces Affinity and asks them to create a new account.

@mattewing
Copy link

+1 to what Jonathan said :)

Austin: I think we could soft launch w/o this if we had to. But, we'd have to explain it to every user because it's confusing. So, it's not ideal. (but better than waiting another sprint cycle for the soft launch)

@aguestuser
Copy link
Contributor

PS: @jlgoldman , @mattewing : apologies for the confusion in my original response. i had in mind the user flow from the groups/1/subgroups/new page (ie: the group creation flow), which logs in a user, etc. the user flow jonathan described does NOT do that and IS confusing.

as noted in the google doc where we were discussing this, it seems like there's a mini-epic about clarifying first-time use user flows that could use some considered thought.

i'm going to defer writing or playing any cards in that epic until @Matt-Holland is back (today!) and we can devote proper analysis and UX design work with @tyesha to thinking that through.

thanks though for the valuable user-testing! very on-point feedback all around! 👍

@Matt-Holland
Copy link
Contributor

Solution option one: treat members just like Organizers -- ask for a password upon signup, and then log them in automatically.

Solution option two: DON't ask for a password, assume most members will never log in, and instead dump them on a public group page at the end. maybe send a welcome email.

@Matt-Holland
Copy link
Contributor

NOTE FOR FUTURE: different groups will want different solutions, should / can this be feature flagged???

@aguestuser
Copy link
Contributor

closing as duplicative of work scoped in #611, #612, #613, #614

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants