What login options do you offer in your app?
Currently in RSVP Keeper I'm just using the normal self-hosted email/password route for the user login, although I'm thinking about adding another option or two based on what would make it easiest for users.
I'd like to know if anyone is using an
Trending on Indie Hackers
I offer Email, Facebook, Twitter, Google. If the product is related to developers/designers I would implement also Github/Dribbble.
Ok - yea it seems like email, facebook, twitter, and google are a good group. I see that's what IH offers as well.
I have had great success using Auth0. Correctly set up, it takes all the complexity away with their lock widget or their hosted login pages. All you need to save is a user token. Auth0 handles all the signup, password reset, all those things you ALWAYS have to build yourself.
The service has been instrumental to our growth and security over the last two years. We literally have no access to users passwords, as Auth0 manages that for us. They offer all kinds of social logins, and it has been nothing but reliable. Using Identity-as-a-Service, all security and privacy concerns are handled by a company that has dozens of engineers dedicated to data security and intrusion prevention.
Also, Auth0 has this wonderful feature of integrating with haveibeenpwned.com, checking if people sign into your service using leaked credentials (and then blocking the attempt). It is wonderful. They have a great API that you can integrate into your backend, and it can easily update/retrieve account information, even merge accounts and things like that.
Pricing is VERY fair. We didn't pay for the first year of using the service, running on the free plan. And we upgraded only to have access to support should we ever need it, which we didn't yet. Our company is at $50k+ MRR, and we pay less than $100 for this service.
I highly recommend it.
Interesting. I've used Auth0 before but found the complexity to be as bad or worse than a good oauth library. Their prices were far higher then than now, too. Maybe I'll take another look at them, at least for apps with small numbers of users.
I really enjoy not having to save passwords on my own system. Immediately a gain in security. The OAuth is really just icing on the cake.
Awesome, thanks for sharing. You know, I've seen Auth0 many times in me dev career but always felt like avoiding it because of having to pay - sorta thinking like why pay when you can roll your own - or thinking that you'll be stuck if you get a lot of adoption.
But it's interesting to hear that you only pay $100 (I presume per month) for a good amount of users that gets you good MMR. That's encouraging and makes me wish I had considered it more seriously.
It looks like I'll be adding facebook and google options soon, I think that'll help round out my login offering. Thank you.
It's super quick to integrate, AND it can also authenticate against you own database :) Never too late.
Free plan has 7,000 free active users. That is more than enough to get started. And the cheapest plan for 1000ish will cost you around $25/month with all the fancy features, custom domains and so on.
Next thing I build, I'll use this service again. Clear winner. Selecting a cloud provider will take me longer than selecting my auth provider :)
That said, I use the Lock.js integration and offer Email/Password, Facebook, Google, and Twitter logins.
We are a B2BC SaaS, selling to teachers. They seem to really love Facebook and Google login.
Auth0 offers Github, LinkedIn, even Dropbox as OAuth providers, listed here.
(I am not affiliated, just a big fan)
I'm using also Facebook login. Many people prefer that because they don't have to deal with passwords, forms and email validation.
Other popular logins are twitter and google
Nice - yea I’ve seen and even used a few of these other options myself as a user - but I was just curious about the actual adoption rate. Do you find that users are more likely to use the email login or the Facebook one?
If you're using Facebook only for basic data (nowadays this is limited to name, facebook id and email) i think people tend to go with this because it's a faster process.
But maybe it also depends on the project.
In my case the registration ratio is higher for facebook login (57.85% from a total of 15908 users).
Great - thanks for sharing that.
Wow, that's a large usage rate for the facebook login - very interesting. I'm def leaning towards adding at least that option..
No problem!
Yes it is!