Live data from Hacker News

Don't make customers hunt for the Sign In button on your website

blog.stunning.co

171–180 of 213 posts

Re: Don't make customers hunt for the Sign In button on your website

#171
This is about the most agreeable HN post I've seen in months. WHY? Why do they do this? Why does every single "new" and "cutting-edge" idea has a website that takes me more then 30 seconds (absolute worst case) to find the very thing I need to login?

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?

Re: Don't make customers hunt for the Sign In button on your website

#172

I find it hilarious that this article is on a SaaS site's blog and has no sign-in button. Maybe I missed the "why this doesn't apply to this site" portion of TFA, though.

Their blog has no sign-in button. Their main page (https://stunning.co/) does.

Re: Don't make customers hunt for the Sign In button on your website

#173
post #156
post #150

Earlier quoted context omitted.

As a non-native English speaker I always confused "sign in" and "sing up". I would prefer totally different words like "Enter" and "Register".

Yeah, those two phrases look too similar. What happened to good old "login" anyway?

from 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.

Re: Don't make customers hunt for the Sign In button on your website

#174

AWS and recently Cloudflare too

As an AWS consultant, I work with a lot of client companies and I’m often watching a screen share while they are navigating through the console. I haven’t seen one yet that actually logs in to AWS directly and not use some type of SSO solution.

Re: Don't make customers hunt for the Sign In button on your website

#175

Earlier quoted context omitted.

They could just check if the username needs to be redirected, and if they do then ignore the password. It wouldn't be that hard. The only downside is the user submitting a password they dont need to, but if you're using js you could post the username first and only post the password if needed. That would be the same exact process, except from the users perspective it would be seamless. You could even have it check th…

this is exactly the sort of thought process that leads to terrible login flows. yes, it's technically possible, and it works for you. but the login flow is one area of your product that needs to work for everybody . There's plenty of features that can be tailored to a power-user workflow because they're the only people that will see it, but the sign-in flow is not one of those. any confusing UI in your sign-in flow i…

Well for facebook, and any other big ones they could just click "sign in with facebook" thats common enough.

The problem is when you have a bunch of enterprise customers and you're not sure which custom login to use, and you dont want to list all your clients.

Ideally, this is solved by the client company telling its employees to use an internal link that authenticates and redirects. Though I'm sure not all clients are capable of this, and still want to use SSO. In that case, I think my solution is much nicer than requiring a two step login.

Re: Don't make customers hunt for the Sign In button on your website

#176
post #171

This is about the most agreeable HN post I've seen in months. WHY? Why do they do this? Why does every single "new" and "cutting-edge" idea has a website that takes me more then 30 seconds (absolute worst case) to find the very thing I need to login? 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…

> Why do companies like Twilio make me put my email in first and hit the arrow before i can even type in my password?

Because of lazy UX implementations of SSO.

You'll see logins like Google, where this is common. If you submit an email that has an SSO authentication associated with it, they can redirect you to the right auth form.

However, for everyone that's not an SSO login this is a worse experience.

Re: Don't make customers hunt for the Sign In button on your website

#177

Earlier quoted context omitted.

You 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.

1Password manages to handle this just fine, even without the hidden password field trick. Perhaps we just need better password managers.

Even 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.

Re: Don't make customers hunt for the Sign In button on your website

#178
post #71

Earlier quoted context omitted.

Inconveniencing either current or prospective customers never ‘makes sense’. It’s not like you have a fixed amount of inconvenience you have to distribute.

You have a fixed amount of screen real estate on the landing page. Distributing it to your most important users for that page (prospective users) does make sense to me.

Is the solution presented in the blog to utilize a cookie to determine if someone is a prospective user versus already a user not an acceptable compromise?

It seems rather straightforward to me, from their example, to de-emphasize the "Sign Up" button and prioritize the "Sign In" button for someone who already has an account.

Re: Don't make customers hunt for the Sign In button on your website

#179
post #171

This is about the most agreeable HN post I've seen in months. WHY? Why do they do this? Why does every single "new" and "cutting-edge" idea has a website that takes me more then 30 seconds (absolute worst case) to find the very thing I need to login? 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…

I've noticed this for years, and always wondered "Why?" myself. Then I came across a UX blog where the author suggested doing exactly this. Their reasoning being that new users aren't familiar with your website, so they need a big garish button to help them sign up easily, whereas regular users are familiar with your website already so they will know where the Login link resides.

I don't agree with it personally, I think it reflects an organization where marketing is prioritised over customer happiness.

Re: Don't make customers hunt for the Sign In button on your website

#180
post #71

Earlier quoted context omitted.

Inconveniencing either current or prospective customers never ‘makes sense’. It’s not like you have a fixed amount of inconvenience you have to distribute.

You have a fixed amount of screen real estate on the landing page. Distributing it to your most important users for that page (prospective users) does make sense to me.

I can’t see how people that already pay me money could not be the most important users?
Post reply on HN