9 ms·
A general rule of thumb I've built up over the years: resist the temptation to innovate around login! Look at the most commonly used flows that are not obvious
by simonw 4y ago
A general rule of thumb I've built up over the years: resist the temptation to innovate around login!
Look at the most commonly used flows that are not obviously terrible and try to implement as close a match to them as possible.
When I've tried to innovate around login in the past I've found that any clever ideas I come up with inevitably run into road blocks pretty quickly.
Here's one example: why have a separate login form from a signup form? They both involve asking the user for an email and password, why not have one form that can do either depending on if the user's account already exists?
I quickly learned why: if you don't understand the user's intent when they submitted that form, you can't show them error messages that match their mental model as to what is going on. This makes for an incredibly confusing experience the moment you step off the happy path.
----
That's not to say it's not interesting and valuable to think through new login mechanisms. They're very interesting design challenges! But its good to be prepared to find out that vanishingly few innovative ideas will work out as genuine improvements.
- PaulHoule 4y agoThat’s what I used to believe. Circa 2000 the advice was ‘do what Yahoo! does’ and that was good, but when I revisited that in 2006 I found that Yahoo’s signup and login process was deformed by the need to discourage users from responding to phishing attempts —- a bank needs to be concerned about this but it will hurt the login for other sites that have higher iq users and aren’t big enough that spamming everybody is a good tactic. I worked on one site (a chat service for Brazil) that had a 20% success rate for the login flow at first that we got up to the high 80s by tweaking this and that. Later I worked on one aimed at scientists that was in the low 80s before optimization. Some tweaks from a long time ago are: 1. Put something like ‘we sent a message to <b>your.email@somewhere.net</b>‘ on the post-registration form where they are likely to see it if they make a mistake. Today forms are likely to ask for your email twice to catch this, annoying as it is. 2. Put a form field for the registration code on that form, we found that oriented people towards looking for a registration code. We still sent a link to click on but we found that users preferred to type the code into the form which was fine with us because they succeeeded. 3. Always store the current URL that the person clicked ‘register’ on and store it in the database so they end up where they started after the process is complete.
- conductr 4y agoI once built exactly what the author proposed and it worked but confused users a lot because they’d have never experienced it before. There was a lot more leak in the signup funnel as people would just leave once asked to do something besides giving their (usually auto filled) info. So I tend to believe trying to generally match the flow they are accustomed to is the best way, even if you think it’s not the best way.
- marcosdumay 4y ago> When I've tried to innovate around login in the past I've found that any clever ideas I come up with inevitably run into road blocks pretty quickly. Either that or you are throwing roadblocks in your user's way. Even if there is no reason for the most common UX to be the way they are, it is what users are used to, and know how to deal with.
- neetcode22 4y ago100% agree with you. I've gone through the entire journey of experimenting + building my own authentication to using a reliable open source solution. Been using this passwordless login recipe by supertokens for my recent projects: https://supertokens.com/docs/passwordless/introduction https://supertokens.com/docs/passwordless/introduction Re-inventing the wheel calls for a lot more than usually anticipated. Best to keep it simple - and if you do end up innovating might as well open source it or contribute to an already popular OS solution.
- djbusby 4y agoHaha, the mistake I've helped implement thrice. Two forms, always.
- melvinmelih 4y agoWhen I started on my first project as a junior engineer I thought I was being clever to build an app without any passwords: every time you wanted to login you received a new email with a link to log you in. Technically, this worked great but after a while I received many complaints from frustrated users who kept looking for the “signup form”…
- webmobdev 4y agoAmazon does this! Morons will ask you to "click the link in the sms" to "authorise access". I can understand doing this randomly once or twice, for security. But every single time!? Figured they were doing it for two reasons - data-mining (to figure out what mobile phone and mobile browser yo have, and to leave an Amazon cookie on your mobile browser), and to harass you into installing and using the Amazon app instead of the website. Had to call customer support multiple times before this stopped (who kept urging me to install the Amazon app).
- smt88 4y agoYou can solve this problem without a signup form. Just give the user two links: sign up and log in. Both ask for email address first. The next screen tells them to check their email. You can use unusual flows without confusing users as long as you give them cues about how to do what they're trying to do.
- drawfloat 4y agoThat doesn’t solve the issue of passwordless login, though, which is the fact not everyone has access to their email on every device at all times. Need to check something attached to a work email (hello Slack) but purposefully not got work email set up on your personal device? Good luck
- solarkraft 4y agoIt's not only having "access to your emails", sometimes these services will send links that are supposed to open in an app and do something there. ... and it just doesn't work.
- nsgi 4y agoThe standard login/sign up form is broken, though. People will just use the same password across websites or write it down. You can't win
- chedabob 4y agoHopefully this should change over the next few years with both iOS and Android adding support for FIDO Passkeys. It's not new tech, but now that two huge players have put it in the hands of millions of users, it should pick up speed.
- m00x 4y agoUse a password manager. Problem solved.
- antioppressor 4y ago
- forty 4y agoDo you also use one computer per account? ^^
- antioppressor 4y agoWhy store passwords that are only used once per half a year with other passwords?
- Karellen 4y agoWhat's your preferred password management solution, and what do you see as its pros/cons over a dedicated password manager?
- pmontra 4y agoI do and tell people to do the same. Unfortunately we can't force people to actually do it.
- HWR_14 4y agoFor your example, this seems bizarre. Every "sign up" process I can think of ends with you being signed into to your new account. Every "log in" process includes a button or link that says "are you a new user, sign up here". You chose a very streamlined thing to worry about.
- osullip 4y agoI'm not sure. A lot end up sending an email that you need to click on to verify.
- HWR_14 4y agoThat's a step of the signup process. AS this article points out, that link ends up with you back in your browser and logged in. In fact, that's probably the most important reason to bring you back to the browser - so you end in the logged in state and can memorize the password in your browser.
- ozim 4y agoSuper typical developer thinking :) two pieces of code look the same but are not doing the same things. I usually see it when people implement add/edit for some entity, that should be separate forms but are crammed into one to be "DRY".
- edgyquant 4y agoThis is why views are so nice. You can reuse the view and controller logic and only write a new data model that updates instead of creates (tbh though those can just be two functions on some data model.)
- eurasiantiger 4y agoOn the contrary, CRUD forms are an ideal candidate for being schema-driven.
- ghayes 4y agoPUT versus POST
- samus 4y agoIndeed; as soon as the article stated that SPF and DMARC are required, it stopped sounding like a good idea.
- LinAGKar 4y agoSounds like a lot of people would accidentally create new accounts.
- makeitdouble 4y agoPeople do go back to the signup page a lot. Redirecting them when detecting an existing account from the email is enough in the most common cases. Users doing "clever" stuff like a random email each time, will also probably understand the situation when they go write down which email for which domain they used and see another entry next to it. There will be some numbers of users that can't be caught and will create many new accounts, but if thwy use your seevice that much, it will probably stop at one point. Nothing is foolproof, but there can be many ways to mitigate the issue.
- deadbunny 4y agoThere is a site I use that does this. I try and use $sitename@domain.tld as the email for most things I sign up to. Occasionally this gets wonky like the site in question because it was originally a Patreon sub for access so the email for the site was patreon@domain.tld then they switched to their own payment system but my email for them is now locked to patreon@domain.tld. So when I log in with sitename@domain.tld it thinks it's new account and just signs you up as a new user rather than saying you don't have an account. Now imagine having a bad day and you try and sign in with 5 different emails because you forgot wha one it was and snow you have 5 different "new account" flows with all the bullshit +12+24+48 hour onboarding/retention/marketing emails for all 5 email addresses. My fault entirely obviously but it is a little mad.
- kqr 4y agoAt the same time, the whole idea of a shared secret instead of asymmetric crypto is source to so many leaks that I wish we would pressure services to not use password-based authentication as their default.