Product Development November 13, 2020

Is Social Sign-in worth it?

Sebastian David Lees @datablast

I recently launched a beta of my product (Datablast), with the standard 'sign up with a user / password / email' combo.

I'm trying go gauge the importance of adding social sign up - it's likely I'll do it at some point in the future, but just HOW important it is?

Has anyone had any experience of drastically improved sign up / conversation rates after implementing social sign up?

My gut feeling is that it won't actually affect sign ups too much - I always hesitate to use social sign in and prefer to have a dedicated account for every service I use. However I could be an outlier!

  1. 4

    Google auth has been great for me. Tons of my users use it.

    I also had FB, Twitter and Slack login previously. Nobody used those.

    Now my login is just google or email.

    1. 2

      I've seen people say that adding Google sign-in (in addition to email) has increased their conversion rate by 10 to 25%... so it's significant but not earth-shattering.

      Probably not a high priority to implement right now for you, but probably worthwhile once you start getting real traffic.

      1. 3

        10% increase is not significant? xD
        Dude that's pretty easy to implement and for 10% hell yeah.

        1. 2

          All I'm saying is that in the early days, if you're getting just a few signups then 10% isn't significant. Once you're getting hundreds of signups then yes, go for it.

          Also depends on the implementation. If you use something like Firebase Auth, it will quick. But other auth implementations could take a lot longer and may not be the best use of time when, for example, you're struggling to get users and signups in the first place.

    2. 1

      Thanks! Have added Google and Twitter to test the waters!

  2. 3

    Offer:

    • Google for business
    • Facebook on social sites
    • GitHub on dev sites

    Does not seem necessary to plainly do them all. And even them think hard about if they are really worth it for you or not.

    1. 2

      Honestly, Google, Facebook and Twitter should be present on all sites with user sign up. A lot of developers use Gitlab or Bitbucket, so you would potentially lose users only offering GitHub.

      1. 3

        Then they always can use email. If you give me 5 options at ones, I won't remember what I used to sign up at all (I have all accounts you mentioned). Going with the email route + one social that makes the most sense is the best start in my opinion. Also much easier to maintain.

        1. 1

          Good point - the paradox of too much choice can hinder in some circumstances!

    2. 2

      This is my go-to criteria.

      Email or Google Sign-in has worked best for my projects. The reason I always give the email/password option, is that there’s plenty of signups coming from non-Google accounts. Specially SMBs.

  3. 2

    Mine is an app for learning Japanese. I just implemented Twitter login this Monday, no one has used it yet. But I already had Google and FB and since I've implemented them, I think half of the new accounts were created with Google. Facebook is used way less and the rest is the default username+email. If you can implement them, I'd say go for it. There's really not much to lose (if anything)

  4. 2

    Well imo there should definitely be a Google Sign option. It isn't that hard to implement and you can find a bunch of tutorials and resources online.

    Keep in mind if you want to publish any app on the App Store that has any social login option available, you must also enable "Sign in with Apple". Otherwise Apple will reject publishing your app.

  5. 2

    As a user, I strongly prefer social sign-in at least as an option. My first choice is Google but Twitter is also acceptable. Facebook is a deal breaker.

  6. 2

    I don't have any data to back this up, but I believe that any site offering user sign up should offer social authentication. A lot of people don't want to sign up with their email, confirm their email and then sign in again; a lot of people just want to click a few buttons and be automatically signed in

  7. 2

    I would suggest to go with Google signin as a default one.

    Additional social logins are worth it depending on the type of service you offer.

    For example, if you offer a developer oriented service, i would add GitHub login, if you target consumers instead, might be worth it to add Twitter login as well.

    Since many users still don't feel comfortable in using Social logins, the good old username - password mechanism is still the most used one.

  8. 2

    If your product targets the privacy-focused users, you can use the "Sign in with Apple" or the "Sign in with SimpleLogin" (my product :D).

    When integrating Facebook/Google single sign-on, these big techs can know when users are on your website even if they haven't clicked on the login button. I wrote an article on that on https://simplelogin.io/blog/do-not-use-facebook-sdk/

  9. 2

    Facebook Login: No
    Google Login: Yes

    Facebook Accounts are unstable and developers keep losing their account for nonsense reason and majority of users are on mobile.
    But on PC good number of people already logged into Chrome with GMail. So unintentionally and intentionally login using Google if they see a Login via Google button.

  10. 2

    Yes, implementing social authorization for every new app isn't fun. I heard AWS Cognito helps a lot with all this logic, but I haven't tried it myself yet.

    1. 2

      If you use Django, integrating social auth becomes second nature after your first few implementations using django-oauth, and I believe Rails has something prebuilt completely in for social auth

  11. 2

    If there isn't a google sign in button then I usually won't be bothered to sign in actually. I think Indie Hackers didn't have it too for a long time, but they have it now and I always log in using google. Usually with service specific account I forgot my password and I have to request for new password every time I want to do something which is really annoying.

  12. 2

    Here's how I respond to sign in flows in new apps I come across.

    I'm more likely to sign up and try it, if there is a Apple/Twitter/GitHub OAuth way. The permissions the app require will tell me how serious they are about privacy.

    I'll use a new email and password combo, only if I had already known the app and I really want it now. Other times, I just check out the app using third party OAuth.

    If I find it useful, I'll later connect my email and create a password. But some apps lack this support to later connect an email and I end up creating a new account with email/password.

    If I don't find it useful, I'll revoke access and move on.

    And as @onenull pointed out, it depends mainly on the product and the type of audience.

    But personally when I am building a product, I would give users the choice.

    1. 2

      Thanks - this is really helpful. I believe you're correct with 'Giving users choice', so am going to go for a couple of options.

  13. 2

    I think it depends on the product.

    As a technical individual/SWE I hate social signups and prefer user/email/pass combo. Reason being, if you ever were to lose access to said social media account, you also lose access to accounts you used the social media account to sign up with.

    I don't think the non-technical crowd cares as much as I do, I'd say gauge your audience. Looking at your product, I'm guessing you're B2B? My 2 cents -- I don't think it's worth it, especially if that's the case.

    1. 1

      Thanks - this is really helpful. Going for Gmail + Twitter. Hopefully that will strike a nice balance as the product is aimed as B2B primarily.

Recommended Posts