3
5 Comments

ASK-IH: What oAUTH sites do you use that users are comfortable/familiar with?

Some sites like dev.to use GitHub as an auth source, I can see how that's easier/faster than doing the whole email/username/pass/click email to validate from scratch.

And I suppose it depends on the niche/field you're working with... I'm not sure for example offhand if you can use say Instagram or Twitter maybe for oAUTH. I've seen Google/Gmail be used so I guess that could be pretty common.

Wondering if anyone here has dealt with login forms a lot, what do you see works best/lowest "friction". This is for content that's tied to users.

on November 24, 2019
  1. 1

    If I were going to start Plunker again, I would probably go with Auth0. I'm not adding value through a homebrewed login flow and increasing risk doing it myself.

    Of course, I do work for Auth0 so I'll caveat this recommendation. But objectively speaking, I believe I would still recommend Auth0 even if I had no relationship with the company. Especially if I was planning on moving into a B2B use-case where single-sign-on might be a major value add.

  2. 1

    Google and Twitter are pretty easy to get working. You should absolutely use an existing library to handle the OAuth flow.

    I've been planning on adding Sign in with Apple as well. Could be useful especially if you have a lot of mobile users.

    1. 1

      use an existing library

      Oh yeah, $npm install my-life ha

      Alright Google and Twitter thanks. The Apple thing is interesting, I'm currently working on a PWA so not quite an app but it would be mostly mobile facing.

  3. 1

    The typical trio is twitter, facebook, google in general case. If your product provide any benefit to the users by connecting these sites, for example integration to google services, sharing content to twitter etc, than users prefer to user these logins and implementing them is necessary anyway and many times you can even ignore email/pass auth. The same logic goes to developer tools or developer focused sites where the github, gitlab, bitbucket trio is the most common auth alternatives. If however, you are building paid SaaS users and developers still prefer email/pass as a primary auth method even if they ask social connection later in the app. If you plan to implement any of these alternatives to email/password, I would recommend using services like firebase auth, auth0 or amazon cognito to simplify the implementation and eliminate some security mistakes you easily can make if you roll out your own solution.

    1. 1

      Thanks for the info. That seems to be the consensus about using an existing library(hopefully free?) But yeah I would intend to have both eg. oAUTH and the typical email/pass. Currently no specific benefit other than not creating another email/pass for a new site.