13
6 Comments

Increased sign-ups by adding 'Sign In With Google' option

We've been focusing on improving the conversion funnel for Reflect, which for us has meant analyzing where users are falling off on the purchase path and coming up with hypotheses on why that's happening and how we can improve.

Still more to do, but wanted to share that adding a 'Sign In with Google' option was a total winner for us. We added this sign-in button to our homepage, sign-in, and registration pages. Since then we've had a marked increase in conversion rate to free accounts, and over 80% of new sign-ups used the Sign In with Google option instead of registering with a username / password.

https://i.imgur.com/btgaR0E.png

Something to consider if you're looking to increase sign-ups!

  1. 2

    Really interesting to see! Glad this worked out for you.

    What are the requirements for adding Google sign-in to your site? Do you have to load a bunch of javascript on your homepage?

    1. 1

      Good question. It mainly depends on how you've implemented authentication and user management on your site. We use AWS Cognito so the implementation wasn't too bad - basically 3 days worth of (mostly) frontend work to hook into the right parts of the Cognito API, add a new screen that handles the back part of the OAuth2 auth flow, and adding the new sign in buttons.

      I assume if you're using a no-code platform like Netlify then this is an easier implementation. Definitely will take longer though if you're not on a platform that already supports it or are already integrated with an identity provider like Cognito or Auth0.

      1. 1

        Thanks, had never heard of Cognito. AWS has so many services!

        Nice that you can use an oauth flow. I built a toy site this weekend that authorizes with Google (usersentry.com) and was not impressed with the performance of the javascript library.

        1. 2

          AWS's JS library is in the same boat performance wise. Their JS library is called AWS Amplify (there's like a million branded AWS offerings at this point) and it pulls in a ton of unnecessary dependencies. We're only pulling in the part of the library that we need (just their 'auth' piece) but it's still really bloated and takes up the majority of our webpack bundle. Thankfully they have a new version coming that's refactored it in such a way that webpack can tree-shake it which slims the bundle size a lot. But yeah, it's surprising that performance isn't a bigger concern for these folks.

  2. 2

    This is great to see, congrats on the improvement! I currently have a product that only allows sign in with Google (timeblocks.co). And considering Apple and Google have a market share of 99% for smartphones, we might soon see much simpler log in flows that show either "Sign in with Apple" or "Sign in with Google".

  3. 1

    Thanks for sharing, 80% is pretty high!

  4. 2

    This comment was deleted 3 years ago.

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 49 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 29 comments My Top 20 Free Tools That I Use Everyday as an Indie Hacker 16 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments