by rfelix2121 on 5/3/21, 1:01 AM with 209 comments
by jillesvangurp on 5/3/21, 9:41 AM
- 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.
by young_unixer on 5/3/21, 8:08 AM
When you receive an invitation to a server, you're presented with a textbox that reads "What should everyone call you?" and you're unknowingly creating a new account. Then you're asked your birth date and then for your email. You type your email and it's already used, obviously.
By this point you don't want to go through the whole process of deleting your browser history to log into your existing account, so you go along with the new account thing and use another email address.
Before you know it, you have 5 different accounts and don't remember which ones you use for which servers.
Yes, there is a "use existing account" link, but it's not prominent, the "What should everyone call you?" textbox with the big "Continue" button are the only psychologically viable option unless you've already gone through the whole process of involuntarily creating many accounts.
by epistasis on 5/3/21, 2:16 PM
And if you do this to people just because their cookie went stale, then is this really a customer that you want to remind that they don't use your service enough? A customer that is happy paying the bill every month but doesn't use a ton of resources?
It reeks of really bad optimization of metrics: do everything possible to increase conversions, at any cost to the rest of the business. That sort of desperation is not good for retention.
by blntechie on 5/3/21, 5:57 AM
by hellotomyrars on 5/3/21, 5:38 AM
The trend of the not having a log in button and only a sign up button, requiring multiple clicks just to login. I get that less friction for a new user is better being the thinking but I truly hate having to go through multiple pages just to sign in.
What happened to having sign in/sign up being on the same page? Seems the simple and easy, as well as lowest friction way of splitting the difference between new and existing users.
by mhdhn on 5/3/21, 5:24 AM
by smcl on 5/3/21, 10:27 AM
While they say "Don't make customers hunt for the Sign In button...", they've implemented "Sometimes make customers hunt for the Sign In button..." which is arguably worse. It's good that someone else has identified this as a problem (it's annoyed me for a while) I just don't think this solution knocks it out of the park.
by sen on 5/3/21, 5:32 AM
They know exactly why they’re doing though, and I think OP is preaching to the converted. Those doing this don’t need a tutorial explaining how not to do it, they need to lose money (users) until they stop doing these dark patterns.
by ogre_codes on 5/3/21, 5:21 PM
I’m not sure why a site would recommend making an extra click easier when it’s not necessary at all. If someone has ever logged into your site, they should get a login page so they don’t have to do some extra tap. This is triply true if your site is frustratingly slow to load.
Also:
Support password managers. Your damned custom login page BS might be cute in design but sucks for usability. If your site doesn’t work reasonably well with a password manager I won’t come back. US Bank lost my business this way recently.
Related: Have sane password requirements and limits. If my password manager gives you a 32 character password, don’t bitch because it doesn’t contain a number or uppercase character. It’s 32 characters long and unguessable, that should be enough. Also... if you fail because there is an underscore or ampersand, you’ve failed.
by Softcadbury on 5/3/21, 6:54 AM
by hcarvalhoalves on 5/3/21, 1:40 PM
by hparadiz on 5/3/21, 5:55 AM
by FriedrichN on 5/3/21, 9:46 AM
by donatj on 5/3/21, 6:01 AM
I keep my windows in a grid and I end up just making my window wider because it’s easier than using their god forsaken hamburger menu.
by tluyben2 on 5/3/21, 7:13 AM
by fossuser on 5/3/21, 4:09 PM
I feel like there should be some specific name for this kind of thing - design patterns that target new users and suck for existing users. Honeymoon feature?
'First hit is always free' feature? Maybe just 'First hit'? I'm bad at naming.
---
"As they approached the city they could see enormous walls surrounding it. Jonathan noticed a guard standing near the entrance to the city. The guard was shouting, “Sign Up! Sign Up! Sign Up!” and then more quietly, “or Log In.”"
https://zalberico.com/essay/2020/07/14/the-serfs-of-facebook...
by wruza on 5/3/21, 9:31 AM
by kingsuper20 on 5/3/21, 3:01 PM
by nickjj on 5/3/21, 10:25 AM
Their home page on a desktop has 2 equally sized sign in and sign up buttons in the top right. The sign up button is filled and the sign in button is outlined. In mobile view it's pretty bad, they still show both buttons side by side but they're buried under a hundred miles of product links.
Besides the buttons being pushed so far down on mobile, is that design really hard to find the sign in link -- specifically on desktop?
Interestingly enough Stripe has only a sign in button in their nav bar https://stripe.com/ for non-logged in potential customers. I just checked with an incognito window. I guess they determined users who sign up mostly come from the main area of their home page or through another page reached from their nav menu (products, use cases, etc.), not so much from a sign up button near the sign in button.
by cek on 5/3/21, 5:02 PM
by musicale on 5/3/21, 7:08 AM
Why, github, why?!
by blunte on 5/3/21, 9:46 AM
Prioritize features (ideally based on studying user behavior), and make those features present and accessible. Hide the rest, if necessary, behind some menu system or toggle.
The minimalism trend (perhaps a reaction to the early amazingly busy Amazon UI?) has gone too far. One great (bad) example of this is Parabol.co. We use it at my company, and it provides just the right set of features we need. But for providing a relatively small feature set, it seems to go out of its way to make it difficult to know how to use those features. I only mention them because they are a good example of this, but there are countless other services that have user hostile (or frustrating) interfaces.
by usrusr on 5/3/21, 8:45 AM
by ed25519FUUU on 5/3/21, 3:48 PM
The second, more fatal anti pattern is not allowing paste in the password field. There’s simply no way I’m going to memorize random 30-digit password for your website. (I had to use dev tools to actually paste the password). Even though the APR was good we moved on.
by croisillon on 5/3/21, 10:44 AM
by cosmotic on 5/4/21, 4:15 AM
by pypie on 5/3/21, 1:04 PM
by csours on 5/3/21, 3:04 PM
This makes it very clear that 1: fitbit wants me to use the app, and 2: fitbit wants to sell me stuff more than they want to help me.
by jFriedensreich on 5/3/21, 9:50 AM
by spookyuser on 5/3/21, 12:32 PM
by jarek83 on 5/4/21, 3:53 PM
I've peeked into the dev tools to see how Tailwind is used there. And since I'm advocating against using Tailwind, this page seems to be a perfect example what problems it brings to the table. Plenty of elements had to use custom classes to randomly overwrite some Tailwind classes here and there (like .display-3 and .main-headline) or completely avoiding Tailwind, like for the #recovered-revenue-main.
It just shows that Tailwind did not solve issues it was claiming to solve, at least in this project. And I guess it must be a pain to maintain this project since PR reviewer and other coworkers now have to know Tailwind by heart to figure out quickly what really got overwritten and why.
by tailsdog on 5/3/21, 9:10 AM
I know it is a blog but still it's part of the website and as a customer I should be able to access "Sign In" with one click from any page, right?
by zackkrida on 5/3/21, 2:24 PM
by stunt on 5/3/21, 2:12 PM
SaaS websites, don't make visitors hunt for what the hell the service does.
It's somehow hard for many SaaS websites to clearly explain what their service does. I often have to dig into multiple pages to figure out what the service does.
by MiddleEndian on 5/3/21, 3:11 PM
https://www.miscbeef.com/birdcrab
(blatant self-promotion)
by zero_deg_kevin on 5/3/21, 4:37 PM
by holler on 5/3/21, 6:23 AM
There’s a business service site I have to log into once a month who’ve hidden the login behind a drop down and it’s really annoying!
by globular-toast on 5/3/21, 12:30 PM
Back in the day it was the other way around. Sign in was primary and sign up was secondary (often accompanied by something like "don't have an account? Sign up"). You just know some busybody UX person saw that and argued this was bad for new members. Well now you've just screwed it up in the opposite direction. Well done.
by SLWW on 5/3/21, 4:39 PM
Why do companies like Twilio make me put my email in first and hit the arrow before i can even type in my password? (it confuses me and the password manager) and adds at least 5 seconds to the login process.
I ask... why?
by ethanoler on 5/3/21, 1:27 PM
The idea is that benefit of having a better CTA for SIGNUP far outweighs the friction/cost for the obscure SIGNIN.
Existing Users can also be trained and conditioned to look for the sign in. They will not get away since they are existing customer (SaaS).
However, once a prospective new lead bounces out, most likely they will not convert anymore (counting remarkerting aside)
by AlchemistCamp on 5/3/21, 5:40 AM
by jarek83 on 5/4/21, 3:40 PM
by poisonborz on 5/3/21, 6:00 AM
by jasfi on 5/3/21, 6:06 AM
by baybal2 on 5/3/21, 1:42 PM
Who in the world came up with this?
by darkwater on 5/3/21, 6:16 AM
by Arhaan on 5/3/21, 4:15 PM
by cpcallen on 5/3/21, 10:12 PM
by metalman on 5/3/21, 12:01 PM
by dreamcompiler on 5/3/21, 1:34 PM
by alpaca128 on 5/3/21, 10:21 AM
by jeffreyrogers on 5/3/21, 3:18 PM
by hnarn on 5/3/21, 9:04 AM
by joshxyz on 5/3/21, 6:50 AM
by stadium on 5/3/21, 5:57 AM
by thepra on 5/3/21, 9:33 AM
by PaywallBuster on 5/3/21, 5:16 AM
by fnord77 on 5/3/21, 11:22 AM
by solipsism on 5/3/21, 5:14 AM