3 ms·
Not sure if it was accidental or not, but we ended up with the single simplest sign-up/login I've ever seen. We've even received a few emails from users alarmed
by bane 16y ago
Not sure if it was accidental or not, but we ended up with the single simplest sign-up/login I've ever seen. We've even received a few emails from users alarmed at how simple it is. We're considering adding a few artificial steps (like filling out a profile) so that users feel more like they are creating an account.
1. Click login
2. Choose account provider
3. Grant us authorization access
4. Done - we pull your name and email address from the OAuth information and autopopulate your user profile.
At this point we don't strictly need any more information, and adding more account providers doesn't increase the number of steps. Actually, when we only supported Google accounts we didn't have a step #2.
We may start asking people some more questions, but for now signing up and logging in virtually identical user experiences.
- theBobMcCormick 16y agoThat's the kind of sign up I really like. I hate having to make up yet another damn password, then record it somewhere because I know I'll forget it, etc. I much prefer to use just authorize you through Google Sign-in, FaceBook Connect, etc.
- codenerdz 16y agoOne problem that I noticed is that not all OAuth providers give you the users emails as part of authentication data. Twitter and LinkedIn for instance dont, whereas Facebook does. How do you handle that?
- bane 16y agoThat's a good question. We're planning on adding support for all three of those in the near-ish future. Very likely we're going to have to engineer an additional sign-in step for Twitter and LinkedIn that we don't need from Oauth providers that do provide the info: 1) Click login 2) choose twitter or linkedin 3) if the account is new, ask for name and email address 4) send out confirmation email with account activation link 5) user clicks activation link in the email 6) done The reason for the activation email is that we really really need to confirm the address for our service to work correctly and to protect ourselves from spam. Otherwise we'd just accept what they enter. For Twitter, we may decide to provide a slightly modified version of our service for scheduled tweets rather than scheduled email, but that'll be a ways off. In that case, if I remember correctly, we should get all of the relevant info from Oauth anyways.
- pamelafox 16y agoWe did that for an app, and let people pick from Google, Twitter, or Yahoo. They'd sometimes forget which one they'd chosen (like after being away from a bit or clearing the cache), and then login with a different one and get confused as to why their data was missing. Do you encounter that at all with your users?
- bane 16y agoThat's definitely something giving us some heartburn thinking about. We're going to try and avoid it unless we get lots of customer contacts (and our development schedule is empty), since we're probably going to have to come up with a solution that links accounts at some point. But, at the moment since we support only two providers, and those providers tend to be pretty divisive with little overlap, we haven't noticed any real problems yet.
- jtheory 16y agoThat's what kills me about these flexible sign-ins -- I was locked out of stack overflow for months because I have accounts on all of these providers, sometimes more than one, and I had no clue what I'd used initially. No idea what the solution to this problem is, but I suspect it isn't going away.
- tripzilch 16y agoI have an idea, but I'm not sure if it would be a security risk. Let the user pick a username to go with the ID provider. When you fill in the username, it'll look up (AJAX) which provider was used and offer/highlight that one? The question is, is it a security risk if anyone can type in any username to find out which ID provider it is used with?