Timeline for How to create better user account creation experience for customers who do not want to create an account
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 22, 2018 at 10:23 | comment | added | O. R. Mapper | "Don't Ask Them for A Username" - maybe make this 'prefill the user name field with the e-mail address'? After all, e-mail hosts come and go, and the user has no control over that. Every time I set up a user account somewhere that seems to be identified exclusively by my e-mail address, I'm both confused and worried about what is going to happen to that account (and my data inside), should that e-mail account ever disappear. Will it be possible to still access the account? Will it even be possible at all to change the handle of an existing account? | |
| Oct 16, 2018 at 15:49 | comment | added | Chris H | @DavidKamer but if you already have a gmail account signed in to google services that you do want, setting up a junk gmail account for SSO is one misclick away from linking your primary (and potentially very personal) online ID. I use google/SSO for a few things that started via Android so it was almost necessary (e.g. Strava) but otherwise an email address I control | |
| Oct 15, 2018 at 23:38 | comment | added | anon | @cpburnz I've found plenty off services compelling enough to make a junk SSO account worthwhile. The thing is, I haven't found one that's both worth a junk SSO account, and not worth just giving my real email. | |
| Oct 15, 2018 at 22:04 | comment | added | David Kamer | @cpburnz I'd use google. You can quickly setup a gmail account and sign into everything with it, and it isn't a painful to use. | |
| Oct 15, 2018 at 21:57 | comment | added | ohmu | @DavidKamer I have yet to find a service compelling enough for me to create a junk SSO account. | |
| Oct 15, 2018 at 21:53 | comment | added | David Kamer | @MichaelLai You could argue that users are responsible for their own privacy to the extent of SSO use, but I'd go further and say that you as the developer only has responsibility for how you use their SSO information, not how the SSO service uses it. If something comes to your attention or a user complains, add a "more information" link or tooltip on the page to let them know the implications and/or what data you are storing from the SSO. | |
| Oct 15, 2018 at 21:27 | comment | added | David Kamer | @cpburnz why not creat a junk SSO account? | |
| Oct 15, 2018 at 20:43 | comment | added | ohmu | For what it's worth I refuse to use SSOs (e.g., Google, Facebook, etc.) to login or create an account on any website. You'll get my junk email address, nothing more. | |
| Oct 15, 2018 at 6:17 | comment | added | VLAZ |
don't make them come up with a username and email, one is enough I'd even say that username isn't always needed. If it's not going to be displayed (e.g., having public posting), then an email is enough. Users usually remember their email, so they don't need to remember another identification. If there is a need for username, by the gods, don't make it set in stone at the time of account creation. There is no real reason to.
|
|
| Oct 15, 2018 at 4:33 | comment | added | Michael Lai♦ | +1 I guess this works when there is a 'trusted' network of sites that the user is comfortable with exchanging or sharing information on. However, if the user wants to remain anonymous then what would be the best strategy? And will the users be fully aware of the implications of providing such information of SSO? | |
| S Oct 15, 2018 at 1:56 | history | suggested | Welz | CC BY-SA 4.0 |
better formatting to emphasize the point, added wiki link for SSO (since I had to look that up)
|
| Oct 15, 2018 at 1:47 | review | Suggested edits | |||
| S Oct 15, 2018 at 1:56 | |||||
| Oct 15, 2018 at 0:30 | review | First posts | |||
| Oct 15, 2018 at 6:28 | |||||
| Oct 15, 2018 at 0:28 | history | answered | David Kamer | CC BY-SA 4.0 |