Google has begun rolling out initial passkey support for Android and Chrome. In a blog post published Wednesday, the company said web admins can start integrating the technology into their websites through the WebAuthn API. Similarly, developers can download the latest Google Play Services beta to start testing the authentication standard within their apps.

Google expects to roll out stable support for passkeys later this year, with an API for native Android apps arriving in 2022 as well. The latter will allow you to choose between a passkey and a saved password when logging into a supported platform.

As more apps and websites add support for passkeys, Android and Chrome users will see their relationship with online credentials change. “Passkeys are a significantly safer replacement for passwords and other phishable authentication factors,” Google notes. “They cannot be reused, don’t leak in server breaches and protect users from phishing attacks.”

Creating a passkey on your Android phone will involve confirming you want to make one and then authenticating your identity with a fingerprint or face scan (you can also use a screen lock). Signing in is just as easy. You simply authenticate your identity and you’re good to go. You’ll manage your passkeys through Google Password Manager, where they’ll be automatically backed up to the cloud to prevent lockouts if you ever lose your device.

Since passkeys are part of an industry-wide initiative to do away with passwords, they work across different devices, platforms and browsers. For instance, as you can see in the screenshot above, you can use a passkey stored on an Android phone to log into a website you visit through Safari. With Apple and Microsoft making similar efforts, the web will hopefully become safer soon.

All products recommended by Engadget are selected by our editorial team, independent of our parent company. Some of our stories include affiliate links. If you buy something through one of these links, we may earn an affiliate commission. All prices are correct at the time of publishing.

Source: www.engadget.com