This was spotted by Leopeva64 on X who shared his discovery while going through the code. According to him, this can be enabled right now on the Stable, Beta, and Canary builds of Chrome on Android, but the experimental flag “enable-autofill-virtual-view-structure” will need to be enabled first before the setting can show up. Once enabled, a new autofill option will appear within settings that will allow you to decide between the default (Google Password Manager) or other providers.
In the example above I set Microsoft Authenticator as the default autofill provider in Android settings.
This is how it normally works in the Stable version of Chrome for Android: pic.twitter.com/t4oQ0ZVuQw
— Leopeva64 (@Leopeva64) March 18, 2024
Chrome’s lack of flexibility in this respect was a point of frustration for those who preferred a dedicated password manager. This integration, when released, will streamline your browsing and give you greater control over the password services you use. While a little more polish is needed, users now have more reasons to consider sticking with Chrome on Android.