2
5 Comments

RIP: Passwords - My take on this

RIP Passwords

RIP

For Loggify I decided to not do passwords at all.
I only do Google-Login and Passwordless-Email-Login/Magic-Link

Here's me take on this:

Passwords take longer to develop and build crappy UX

If you have passwords, you need to build all the UX around

  • Password setting
  • Verify Email
  • forgot password
  • change password

Most include sending email and being complicated.
You also always have Signup and Login as different workflows.

What I do instead:

I only have one UX Flow.

Google Login: Click to Login
Email Login: Type Email, click link in email to login

But what if the user is not signed up yet?

I simply create a new user and do the same thing. Google login or sending an email.

And if a user switches the login method?

If a user logged in with email before and then clicks google login: I just log them in. And vice versa.


This way there is never the problem traditional passwords have, emails are simple to send (I do it with Sendgrid).

PLUS: I also create users on the server (if people add users to their company, that don't have an account yet). I simply create the user without a signin method, and first time they use one, I simple add the method to the user :)


What's your take on this?
Feel free to try out at studio.loggify.app

on August 16, 2022
  1. 2

    Yes! I really dislike lengthy sign up processes. I tend to want to use a product to know if it's right for me, so I want to jump to that experience as fast as possible. If you're building a product that requires a lengthy sign up process, I would recommend breaking it up into smaller steps so that the user doesn't feel overwhelmed. You can also provide a progress bar so the user knows how close they are to completing the process.

    In our app (vidon.ai) you can try a mini version on the website, and only require sign in if you're actually going to export a video.

    1. 1

      I love this approach.
      You lose leads along this way a little, but with a great product, that needs little explanation this should be a reasonable compromise

  2. 1

    interesting approach.

  3. 1

    Yeah agreed, also I always try to let the users use the app without signing up. I encourage them to sign up by locking out certain features.

    1. 1

      Depends on the app, if you need to persist state, or have something, where state can be wiped or saved in a URL or something, but yes. Great approach if possible :)

Trending on Indie Hackers
I shipped a productivity SaaS in 30 days as a solo dev — here's what AI actually changed (and what it didn't) User Avatar 259 comments Never hire an SEO Agency for your Saas Startup User Avatar 107 comments A simple way to keep AI automations from making bad decisions User Avatar 71 comments 85% of visitors leave our pricing page without buying. sharing our raw funnel data User Avatar 43 comments Are indie makers actually bad customers? User Avatar 40 comments We automated our business vetting with OpenClaw User Avatar 38 comments