Passkeys + Social logins( Google, Twitter, Meta sign in) product release

3 min readJul 20, 2023


Harnessing the power of social login to migrate users frictionlessly to passkeys

IF you are building an app today that is not a wallet, insurance or medical provider, you have probably implemented social logins. And If you haven’t, you should!! Data shows that Sign-in by google, Meta or twitter increases account creation conversion by at least 25%. The reason is simple: Forced account creation is a buzz killer. No one wants to create a new account for a service/app they are not yet sure whether they will ever use it again!

Unfortunately, lunches (logins) still do not come free, and you are delegating your user identities to these social-media platforms. Meta (facebook login) or Google Sign-in uses this information to track user behaviors across sites and services, enabling them to better target those users for ads.

More so, social networking services are blocked within certain networks i.e. workplaces, libraries, and universities/schools for productivity reasons, or even in certain countries due to censorship.

Now let’s say that you want to migrate your users to passkeys: enabling a faster, higher convergent and more secure login experience. You are not alone. Google just announced support for passkeys in for gmail 3 months ago, and Apple followed suit by transitioning Apple ID login to passkeys last month.

The challenge is how to transition users without complex UX changes that would ultimately result in login fatigue or conversion drop.

Connecting passkeys registration to Social Login Sign-in

We have been working on a solution that we are happy to share today with the community. Introducing social login connector: This basically allows you to register passkeys for all your existing user seamlessly during their typical login flow. Users click on their favorite social login (meta/Google, Twitter,..etc), and once they are authenticated, they are prompted to register for a faster and more secure login the next time.

In essence, the registration happens with minimal friction; no redirects, email links, or complex UI/UX steps for the users.

Demo: Let’s take a look how it works

Passkeys registration during Google Sign-in


The authentication journey next time is just as frictionless: If the user clicks on the email/phone number field, they can see their registered passkeys, click and use their fingerprint/FaceID or PIN code to log-in

Please give it a try below and let us know what you think

Demo link:

If you are interested in integrating this into your web or mobile app, refer to our documentation.