third-party autofill companies assist on Chrome on Android

Posted by Eiji Kitamura – Developer Advocate (@agektmr)

In October 2024, we introduced that Chrome 131 will permit third-party autofill companies on Android (like password managers) to natively autofill kinds on web sites. Reflecting on suggestions from autofill service builders, we have determined to shift the schedule and permit the third-party autofill companies from Chrome 135.

Native Chrome assist for third-party autofill companies on Android signifies that customers will be capable of use their most well-liked password supervisor or autofill service instantly in Chrome, with out having to depend on workarounds or extensions. This alteration is anticipated to enhance the consumer expertise and safety for Android customers who use third-party autofill companies.

Based mostly on developer suggestions, we have mounted bugs, and have been working to make the brand new setting simpler to find. To assist these targets, we have added the next capabilities:

• A capability to question Chrome settings and be taught whether or not the consumer needs to make use of a 3rd social gathering autofill service
• A capability to deep hyperlink to the Chrome settings web page the place customers can allow third-party autofill companies.

Learn Chrome settings

Any app can learn whether or not Chrome makes use of the 3P autofill mode that permits it to make use of Android Autofill. Chrome makes use of Android’s ContentProvider to speak that info. Declare in your Android manifest which channels you wish to learn settings from, e.g.:

<uses-permission android:title="android.permission.READ_USER_DICTIONARY"/>
<queries>
 <!-- To Question Chrome Beta: -->
 <package deal android:title="com.chrome.beta" />

 <!-- To Question Chrome Steady: -->
 <package deal android:title="com.android.chrome" />
</queries>

Then, use Android’s ContentResolver to request that info by constructing the content material URI as on this instance code:

ultimate String CHROME_CHANNEL_PACKAGE = "com.android.chrome";  // Chrome Steady.
ultimate String CONTENT_PROVIDER_NAME = ".AutofillThirdPartyModeContentProvider";
ultimate String THIRD_PARTY_MODE_COLUMN = "autofill_third_party_state";
ultimate String THIRD_PARTY_MODE_ACTIONS_URI_PATH = "autofill_third_party_mode";

ultimate Uri uri = new Uri.Builder()
                  .scheme(ContentResolver.SCHEME_CONTENT)
                  .authority(CHROME_CHANNEL_PACKAGE + CONTENT_PROVIDER_NAME)
                  .path(THIRD_PARTY_MODE_ACTIONS_URI_PATH)
                  .construct();

ultimate Cursor cursor = getContentResolver().question(
                  uri,
                  /*projection=*/new String[] {THIRD_PARTY_MODE_COLUMN},
                  /*choice=*/ null,
                  /*selectionArgs=*/ null,
                  /*sortOrder=*/ null);

cursor.moveToFirst(); // Retrieve the consequence;

int index = cursor.getColumnIndex(THIRD_PARTY_MODE_COLUMN);

if (0 == cursor.getInt(index)) {
  // 0 signifies that the third social gathering mode is turned off. Chrome makes use of its built-in
  // password supervisor. That is the default for brand new customers.
} else {
  // 1 signifies that the third social gathering mode is turned on. Chrome makes use of forwards all
  // autofill requests to Android Autofill. Customers should opt-in for this.
}

Deep-link to Chrome settings

To deep-link to the Chrome settings web page the place customers can allow third-party autofill companies, use an Android Intent. Guarantee to configure the motion and classes precisely as on this instance code:

Intent autofillSettingsIntent = new Intent(Intent.ACTION_APPLICATION_PREFERENCES);
autofillSettingsIntent.addCategory(Intent.CATEGORY_DEFAULT);
autofillSettingsIntent.addCategory(Intent.CATEGORY_APP_BROWSER);
autofillSettingsIntent.addCategory(Intent.CATEGORY_PREFERENCE);

// Invoking the intent with a chooser permits customers to pick out the channel they wish to 
// configure. If just one browser reacts to the intent, the chooser is skipped.
Intent chooser = Intent.createChooser(autofillSettingsIntent, "Choose Chrome Channel");
startActivity(chooser);

// If the caller is aware of which Chrome channel they wish to configure, 
// they will as an alternative add a package deal trace to the intent, e.g.
autofillSettingsIntent.setPackage("com.android.chrome");
startActivity(autofillSettingsInstent);

Up to date timeline

To mirror the suggestions and to go away time for autofill service builders to make related adjustments, we’re shifting the plan. Customers should choose Autofill utilizing one other service in Chrome settings to make sure their autofill expertise is unaffected. The brand new setting will turn out to be accessible in Chrome 135. Autofill companies ought to encourage their customers to toggle the setting, to make sure they’ve the perfect autofill expertise doable with their service and Chrome on Android. Chrome plans to cease supporting the compatibility mode in summer season 2025.

• March 5th, 2025: Chrome 135 beta is offered
• April 1st, 2025: Chrome 135 is in steady
• Summer time 2025: Compatibility mode will now not be accessible on Chrome