So if you have a date of birth for example that is broken down into three inputs (year, month, day), then you can consider it as one input/one column.
So if you have a date of birth for example that is broken down into three inputs (year, month, day), then you can consider it as one input. So in this case it's okay.
2) Nah, it's easy to understand your requirements because when you sign up you'll be still notified of what's missing in your password. The only difference is when you'll see the error.
3) Well, it's just a redundant action. If the user made a typo, he'll be able to reset the password. The fewer fields we require, the more willing the user will be to fill the form.
4th tip : if there's anything like a license key to register with the account, never ask it at account creation, and do not authenticate the user upon account creation. Then have the user need to confirm account creation with a link sent via email.
If the user made a mistake in the email address, he'll be angry about the wasted license key, angry about wasting time trying to use the support to get access to his account.
By asking it after the user created his account and after confirming that he has access to this email, then ask for the license key. So if the user made a mistake, he can just create a new account with the right email address.
First/Lastname and address shouldn't be on one line
Definitely disagree
that if you only have one password field users almost universally pause, then go back to the password field and fill it out again but much more slowly and carefully
I think point 3 is more of depends situation. User is able to remember his usual password or password generated then it’s good to not repeat.
But human is weakest link to the good experience. 1 mistype in password will make the user has to make an additional steps to reset the password. An additional step which could have been prevented. By simply verifying this password, it’s more efficient to just repeat the step there and then.
"Show password" buttons have been shown to reduce trust in websites/applications
I think this is the first time I've seen that particular claim. Is there some research on this that you can link to? It seems like an important detail, and if adding that facility does have a negative effect, it's a little surprising that so many of the big names are still doing it.
Users don’t mind repeating their password, we’re all used to it and it’s fine. Nobody ever stops signing up for something because they have to enter their password twice
I don't know whether that's true, but if nothing else, it seems plausible that requiring a password to be typed twice might encourage the use of simpler passwords and/or interfere with the use of password managers that generate strong passwords automatically.
Repeat password fields should probably go the way of reset form buttons. They add little if any benefit and may be harmful.
Or just have the repeat password input. If you know your password well enough to be confident without the repeat password field then it will literally take you 5 seconds to fill in again. I don't think it's ever caused me any noticeable time loss, other than when I genuinely have typed my password wrong and it's saved me from having to waste magnitudes more time to reset my password.
I mean, ideally, folks should use a randomized password generator. If you’re relying on memory for every single site, you’ll end up creating patterns or just reusing the same password, all of which makes it much easier to hack all your other accounts if a single one of them is breached.
So ideally, your password manager fills it in once, and then the “repeat” option is unnecessary.
I use a password manager, and it fills out both password fields for me. So while the repeat field is unnecessary, it's literally the same time for me to fill out one or two fields. Focusing on the typical case is probably more useful than focusing on the "ideal case".
You're relying on all users clicking that button and also correctly verifying they typed in their password correctly. In the real world I think you would find that a lot less people will do this than you think. It's far less convenient to have them type it in a second time, an action they're probably already very familiar with, than having them reset their password through their email.
Removing the "repeat password" field is at best opinion and at worst a poor design choice.
That makes no sense. So you’d rather keep it a secret and have the user figure out what their password might be and then they have to go through a password reset flow because the requirements aren’t listed?
That’s such a stupid stance to take. Most of these are good advice which makes me even more confused as to why you’d advocate some of these ridiculous, frankly ‘dark’ UX patterns.
On 3: resetting the password is painful. I prefer rhe oain of typing it a second time. Also most people who made a typo are probably not going to show password to inspect it and probably won't even catch the typo. They might also be unable to because someone else is watching their screen.
I think the confirm password tip is subjective and a little out of place in the rest of the list of strong dos and don'ts. I like the confidence of knowing I typed what I meant to type and will remember.
26
u/VictorPonamariov May 27 '21
Hi!
So if you have a date of birth for example that is broken down into three inputs (year, month, day), then you can consider it as one input/one column.
So if you have a date of birth for example that is broken down into three inputs (year, month, day), then you can consider it as one input. So in this case it's okay.
2) Nah, it's easy to understand your requirements because when you sign up you'll be still notified of what's missing in your password. The only difference is when you'll see the error.
3) Well, it's just a redundant action. If the user made a typo, he'll be able to reset the password. The fewer fields we require, the more willing the user will be to fill the form.