![]() ![]() ![]() Again, I can appreciate the intention here: they’re not trying to overload a user with too much info at once. Shopify (another service I love) annoyingly splits its login across three separate screens. When we try to get too clever we force users to learn new conventions which slows them down (at least initially). While I’m not saying we shouldn’t ever innovate, it’s important to recognize users come to your product or service with a lifetime of hard-earned knowledge about how to use the internet. It forces users to learn a new convention – Users learn patterns (login, checkout, navigation, etc) by experiencing them again and again in many applications over many years.But it’s not just about creating consistency within your own ecosystem, it’s about being consistent with the rest of the internet. With the advent of design systems we talk a lot about consistency. This doesn’t work at all with password managers, which is incredibly annoying as I want to lean on password managers to, uh, manage my passwords.Find message from service (if you don’t get distracted by other emails first). I can appreciate the cleverness of this pattern as it avoids the rigamarole of users having to remember yet another password and building out all the “Forgot password” flow stuff. I think this may have started with Slack, but I’m seeing other digital products like Notion (which I love by the way) send users a temporary password to their email in order to login. MacOS login screen also buries the password field to “clean up” the UI (and I’d also assume to encourage users to login via TouchID), but that cleanliness leads to (in my view) a more confusing experience. It’s just one additional, unnecessary hoop they have to jump through in order to login. Users have to exit out of another field in order to expose this surprise extra field to fill. The problem is that field is required, and because it’s hidden password managers can’t pre-fill the field. This feature doesn’t work with modal login forms.ĭelta’s site hides a required “Last Name” field, which I’d assume is to clean up the UI by introducing a bit of progressive disclosure. 1Password has an awesome “open and fill” feature allowing you to visit a website and populate the login form with your credentials. It also prevents password managers from doing their thing since the modal is hidden. Not being able to link directly to the login, which can be a pain for customer support people (since they have to give a bunch of instructions described above rather than simply providing a link).fill out form” rather than visiting a login page (via search, customer support chat, bookmark, password manager, directly, or via the primary navigation) and filling out the form. Hertz and a whole bunch of other sites keep their login form in a modal window or a drawer. ![]() Here are some patterns that I encounter on websites that I think should be avoided. TL DR create login forms that are simple, linkable, predictable, and play nicely with password managers. And then let’s look at some better ways of tackling login. Let’s walk through some login patterns and why I think they’re not ideal. As password managers like 1Password (which is what I use) and Chrome’s password manager (which I also sorta use) become more popular, it’s important for websites to be aware of how users go about logging into their sites. As time goes on I find myself increasingly annoyed with login forms. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |