Streamline Oauth Account Creation
planned
Melissa Zhang
One thing we've noticed during the oauth process is that if you don't have a Rally account, the process is a bit cumbersome. The process includes:
1) User goes to third party dev site
2) User doesn't have a rally account and gets directed to rally to create an account
3) User creates account with email and password
4) User verifies their email and the UI indicates that they successfully created an account
5) User logs back into Rally
6) User is prompted to complete their profile with name and username
7) Users go back to Bonfire and connect their Rally account
We're seeing that if you don't complete steps 5 and 6, then fetching the user info from https://api.rally.io/v1/oauth/userinfo will fail. Is it possible to make the process for a new Rally user more streamlined for 3rd party apps? We have some users who get pretty confused since they don't know that they need to sign in again and fill out their profile.
Possible solutions
* Allow account creation during auth - this is probably the most holistic solution and allows the user to stay in the context of the third party site
* Remove steps 5 and 6 as a requirement for fetching user info - this would remove some steps but the user still needs to leave the third party site experience
* Tell users in step 4 that they need to sign in in order to complete their account - this is probably the lowest hanging fruit though doesn't solve all of the pain points.
Open to any other solutions as well!
Russell Spence
planned
Internal Ticket: https://starcard.atlassian.net/browse/RALLYB-2455
I can see on the other team's backlog, that this item is fifth from the top. I expect something to go out soon.
Not my team, but I expect some improvement here. We'll need to revisit this ticket when the changes go out to see if all pain points are addressed.
Alex Phelps
ESCALATED! Russell Spence
mrq02
Alex Phelps: Glad to hear this is being escalated. This is hugely important to onboarding new users. Lots of people who haven't registered at Rally are hitting third party apps, and the smoother we can make their first experience the better for everyone.
Matt Alston
mrq02 Alex Phelps Completely agree - it feels like new user onboarding is one of the highest-impact places to improve the product experience for all creators/fans, and with the community dev ecosystem growing this will only be more of a challenge over time. Super interested in figuring out an elegant solution here!
Dave Young
Alex Phelps: Very glad to hear this
Bret Kinsella
Alex Phelps: We are working on adding $BOT Coin to a couple of bot apps and this onboarding is a bit overwhelming. More steps than most people will tolerate. As many of us migrate into use cases that actually employ the coins in novel ways in order to enhance their perceived value, the efforts are significantly undermined by the account linking process. I'm sure there are good reasons for why it was a suitable approach at the time the features were implemented. However, today it is a barrier to conversion and therefore a barrier to increased transx volume as well as net new coin purchases.
M
Mike Li
mrq02 you are correct, the account is not fully created until they input their name and username.
mrq02
Mike Li: It seems like (after watching Matt's video) a relatively simple solution here is to have the e-mail verification link redirect to the Rally.io/login on completion instead of redirecting to Rally.io. That gets most of the way there with a very simple change; the user might be confused about what they should do after logging in, but at least nothing will fail. A better (but more complicated) solution is to have two separate account creation flows: one from the site and one initiated directly from the oauth page that sends an email with a different "verify email" link so that it knows to send them back to the correct oAuth callback after onboarding is complete.
Skot Leach
Tagging Russell Spence to get his input. This may need to go to the Rally io devs.
Matt Alston
Here's a quick demo detailing the issue a bit more! https://drive.google.com/file/d/1Z4b2iANJGIzNTELgvjdWMMQCMivrCOGp/view?usp=sharing
mrq02
Does userinfo fail entirely? I would expect it to return at least the wallet id. Otherwise that implies that wallets are created not on account creation, but on first login.
Melissa Zhang
mrq02: Yes we're seeing that the userinfo call fails entirely with an "Internal Server Error" and no other info. I assume it's because having a username is required to transfer coins but not really sure.
mrq02
Melissa Zhang: Interesting. I guess it could also be missing error handling rather than wallet creation on first login. Either one could cause the whole thing to fail.
O
OverAchiever
D
Dave Young2
This is a huge friction point in gaining new users when they're most excited, hope it can be addressed!