2
12 Comments

Signup / Login Flow UX Feedback

Signup / Login Flow UX Feedback

Good morning, fellow hackers!

I wanted to get some feedback on all of your thoughts about a new-ish style of signup/login flow I've started seeing.

I recently started using https://www.notion.so/ as my place for notes and journaling for my indie hacker adventures.

One feature that I thought was particularly thoughtful was their signup/login flow. To sign up, all you need to give is your email address. When you submit your email address, they send you a link that will automagically log you in.

When you return to notion.so, and need to login — you do the same thing. Just submit your email, and you receive a login link.

As a user, you never need to worry about setting up a password. I think that's pretty cool.

It's pretty interesting from a security perspective. They're essentially offloading account security/liability to their user's email provider. In many cases I could see this being a great thing. Gmail has great security features and supports sane/good 2 factor auth. But I could see some users wanting to create passwords for various reasons.

So my question to you all is: Is the signup/login via link in email a good pattern? Should I use this pattern in my own product?

on February 18, 2019
  1. 7

    Brad Frost says it all in one of his recent articles:
    http://bradfrost.com/blog/post/dont-get-clever-with-login-forms/

    I also think the whole process is a bit of a pain. All I want is to have my password manager login for me...

    1. 3

      👌this post sold me. I'll stick with a simple username/password login form!

    2. 2

      This comment was deleted 4 years ago

  2. 3

    I've wrestled with this question in my various Ux roles for a long time.

    My hunch is that though it's secure (more secure than passwords, given what terrible passwords most people choose), it's not a great idea to force signup/login via email link rather than password.

    Reasons:

    • Context switching from signup/login to email is painful for users, especially on phones.
    • There's a problem with making sure when users enter their email address that they're human; Medium and others solve this using Recaptchas, but it's even more painful for users, every time they log in, not only to context switch to email, but to have to fill in an ever more demanding Recaptcha on the way there.
    • Advanced users have the password problem solved, e.g. with password auto-fill in their browser or with 1Password; it's not great to tell them that they have to do it the more painful way instead.

    Hope that helps!

  3. 2

    It's horrible. Why would you force your user to open another app to use the product they paid for? Why would you make them wait for a business critical app if email delivery is slow that day?

    Your job as a service provider is to provide service, not manufacture hoops for your paying customers to jump through.

    It's only an acceptable use if your targeted audience is people who are extremely technically unsavvy. Even then, they have to know how to switch apps. Bad, bad bad.

  4. 2

    Interesting idea. On one hand I like it because it eliminates the need to remember a password, but on the other hand, sometimes email takes a bit to come in and you risk losing the user's interest if they get distracted by their inbox while they're waiting for the login email.

    It's always a risk to adopt a pattern like this that isn't the "standard" flow that your users are expecting.

  5. 1

    I love the idea and it is the way we are going forward with in our project (onefinaldoc.com).

    I see some people don't like this because they use LastPass or 1Password and think going to email is slow.

    Despite that, I still think it is great. One of the pros of this approach is that if you pay the service for your employees, you know they won't have access if you removed their email @yourcompany.com.

  6. 1

    Imo that's the way to go. Security wise, I would not want store any of my users passwords and also users more often than not, are not careful with their passwords. Ux wise, imo passwords is an old pattern, while it may be faster for the user to login, authentication is a one time effort (on each device), and if your app is great, I'm pretty sure no user will mind it. Personally I don't want to maintain any passwords and prefer social auth or magic link/code, given the choice

  7. 1

    One problem with this approach is if the email goes to Spam or otherwise is flagged by Gmail etc. A technical user might know where to look, but a non-technical user might just assume it's not working. Your email setup becomes a SPOF effectively locking users out of your application.

    1. 2

      This and another thing to consider is "time to inbox". I would not want to wait minutes to receive the login email, which can happen.

  8. 1

    I find it suitable and appropriate. An automatic sign in by clicking on email link will make things simple.

  9. 1

    I signed up a few days ago, and spent too much time trying to reset my password.

  10. 0

    This comment was deleted 7 years ago