6 ms·
A couple of frequent mistakes with signin which are usually caused by junior product owners/ux persons not reflecting on what they are doing and blindly copying
by jillesvangurp 6y ago
A couple of frequent mistakes with signin which are usually caused by junior product owners/ux persons not reflecting on what they are doing and blindly copying what they believe is the way to do things.
- Having confusing language and poor differentiation between the sign in and sign up form. Symptom, users start filling in the wrong form only to realize their mistake.
- Separating the password from the email field with an extra mouse click sucks if you are using a password manager. Doubly so on mobile where using password managers involve a bit of fiddly interactions. Having to do this twice sucks. If you do this, at least have one of the fields in the dom tree but hidden so that it gets filled with one click via your password manager.
- Not making the login form password manager friendly my not sticking to conventions for field names for this.
- CodesInChaos 6y ago> - Separating the password from the email field This is useful if you support authentication methods other than password > - Not making the login form password manager friendly my not sticking to conventions for field names for this Instead of relying on heuristics based on field names, it's also possible to annotate the field with the autocomplete attribute https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes...
- kkirsche 6y agoYou can still separate them and have a hidden password field for a password manager to bypass the other page or pass it through to the next page.
- numbsafari 6y ago1Password manages to handle this just fine, even without the hidden password field trick. Perhaps we just need better password managers.
- Nextgrid 6y agoEven if password managers handle the two-page scenario you still have the delay of loading the second page. On high-latency connections this is a major problem.
- emilsedgh 6y ago> Separating the password from the email field with an extra mouse click sucks if you are using a password manager. If I understand correctly, the reason behind this pattern is SSO. Most websites are gaining SSO capabilities. Before asking for your email/user, they don't really now if you're gonna login using password, or you should be redirected to an IdentityProvider. I'd be happy to know if there are better patterns here but I think password managers should get a bit smarter and work with this trend.
- egeozcan 6y agoHonestly asking, what's wrong with "Password (Leave empty if you're using {Name of SSO}): ____"? If you are going to tell that may confuse users, I think not having a password field is already confusing the other half, while also not being password-manager-friendly.
- fckthisguy 6y agoI don't think making the user read instructions is the solution. Most (myself included) will begin typing before they finish reading. The current trend to only show the password box after the username is provided doesn't have to be bad for password managers. I use loads of sites that do this (so they can support SSO) and they just use hidden form fields so the password managers know what to do. I'd be curious to hear any suggestions you have for password managers to improve here though. I can't think of anything short of a .well-defined login route.
- beforeolives 6y agoThe Oreilly learning platform does this. Email and password field on the same page and a message under the email field > Using Single Sign-on (SSO)? Simply enter your company email address and click sign in. Seems simple enough to me as a user, not sure how most people interact with it though or how many companies A/B test these things.
- benhurmarcel 6y ago
- tomxor 6y agoAnother one: - Defocusing input fields in the middle of typing login information I guess i'm in the minority these days but I like to keep strong passwords in my head. This usually happens due to some side effect of the login page being absolutely fucking massive and not fully loading or executing before I start to fill in the form, then one of three things usually happens in order of frequency: 1. cookie banner blocks input and defocuses 2. it defocuses for no apparent reason (I suspect MVC "rendering") 3. it "helpfully" re-focuses on the first input element The last one is the most annoying because in the worst case i type my password in visible text. Only login I regularly use that does not suffer from this problem (or any others!), is HN: https://news.ycombinator.com/login https://news.ycombinator.com/login is 1.07KB Causes only one secondary HTTP request to favicon at 7.66KB which doesn't interfere with the page in any way.
- jan_Inkepa 6y ago> - Defocusing input fields in the middle of typing login information Browser url-bars are shooketh...
- tomxor 6y agoThe great internet speed divide has no patience for loading superfluous crap that is wasting their lives.
- Timpy 6y ago>defocuses for no apparent reason I use Surfing Keys, a vim-like plugin for browsers. When inputs defocus unexpectedly while I'm typing all of the navigation shortcuts kick in and it's like "roll a d100 to see which random negative consequence you get." Usually I at least lose the page that I'm on and I have to start the form over.
- kalleboo 6y agoThis reminds me of when certain browsers used to emulate IE by mapping backspace to "go back". I lost so many forms to that feature before Safari came up with the "are you sure you want to leave without submitting this form you started filling out?" dialog and they copied it
- Aeolun 6y ago> Separating the password from the email field with an extra mouse click I think they mostly do this so SSO customers do not accidentally enter their company password on the site every time.
- johannes1234321 6y agoRight, often those sites have customers with different SSO systems. I type my company mail address and am redirected to company SSO. I like this more than other sites where I have to find the right button between different login options (sign in with google, sign in with facebook, sign in with sso, ...) and then have to type the company name ... whatever might be the choice the admins did there that time ... I also think that approach was initially created by Yahoo! So they could shown the user's avatar on the password page to prove authority. Not sure whether that still is a thing somewhere, considering that a recent trend is not to verify whether an account exists ...
- jonplackett 6y agoThis is always still annoying since you type in your email, then get sent off to your SSO page - and they can never be bothered to post your email over, so now you have to enter it again.
- alex_anglin 6y agoAgreed. It always seemed to me as analogous to the situation whereby one enters some identifying information in a phone prompt, only to have to spell it out again for a CSR. Both are just plain bad design.
- Aeolun 6y agoI kind of agree, but that seems more of a problem with the target system. Anyway my name is remembered on my company SSO form, and I never sign in as someone else.
- thrower123 6y agoI don't know if all of the SSO login sites do this, but Office 365 authentication makes it a huge pain in the ass to get back to the page that you tried to login from; usually you get dumped back to the home page, and have to try to navigate back to where ever it was you were. Azure Active Directory does not make it easy to do this, with the way you have to explicitly whitelist post-back URLs, or else you get the dreaded login.microsoft.com 401 page of death, where you have to parse out information buried in the query-string to determine why you didn't get redirected properly (usually it is a trailing slash on the URL... %2F)
- tyingq 6y agoAlso, blocking right-click->paste is REALLY irritating.
- 725686 6y agoAs a non-native English speaker I always confused "sign in" and "sing up". I would prefer totally different words like "Enter" and "Register".
- kijin 6y agoYeah, those two phrases look too similar. What happened to good old "login" anyway?
- notatoad 6y agofrom the meeting where it was explained to me that we couldn't use "login", it is too technical-sounding and not friendly enough. "log in" is computer language, "sign in" is human language.
- bluedino 6y agoYou want to enter a site you're already on?
- 725686 6y agoAs I said, English is not my native tongue. Choose whatever synonyms are appropriate. Even google translate gets confused. If I enter "sing in" it translates it to Spanish as "registrarse" which is actually "sign up"! How about using enroll, or register instead of "sign up"?
- majormajor 6y agoAt the last big subscription company I was at, it wasn't a product owner seniority thing, it was a organizational problem. Signup is a big thing with lots of stakeholders and interest. User acquisition is an easy metric to track for business health. Everyone wants to push not-logged-in users to sign up. Ownership of logging in was much less clear. It's not a full time job for a person or team in the same way customer acquisition is. So you put some buttons/links on the page, but then there's no single owner of them to get pissed off when other teams start moving their shit around. (The other aspect here is that the website was a declining platform compared to the apps, where a not-logged-in user is much more captive and there's a more obvious single "login or signup" landing page point. On the web most media sites, at least, try to provide SOME sort of preview/partially functional experience version of the logged-in view, which wasn't designed with a prominent "SIGN IN" button in mind.)
- kevincox 6y agoThis is what is screams to me. When I have a hard time finding the sign-in link it says "We don't care about our existing users, we only care about getting new ones." It is a big red flag for me these days.
- yoz-y 6y agoI feel that lately password managers (at leat 1Password, which is what I use) have been working even with split forms. So at least there is that.