Skip to content
Branch: master
Find file History
Type Name Latest commit message Commit time
Failed to load latest commit information.
.google Update packaging.yaml Sep 11, 2019
Application Adds AutofillFramework sample to repo. Jul 30, 2019
gradle/wrapper Adds AutofillFramework sample to repo. Jul 30, 2019
screenshots Adds AutofillFramework sample to repo. Jul 30, 2019 Adds AutofillFramework sample to repo. Jul 30, 2019
build.gradle Adds AutofillFramework sample to repo. Jul 30, 2019
gradlew Adds AutofillFramework sample to repo. Jul 30, 2019
gradlew.bat Adds AutofillFramework sample to repo. Jul 30, 2019
settings.gradle Adds AutofillFramework sample to repo. Jul 30, 2019

Android AutofillFramework Sample

This sample demonstrates the use of the Autofill Framework. It includes implementations of client Activities with views that should be autofilled, and a Service that can provide autofill data to client Activities.


This sample demonstrates the use of the Autofill framework from the service side and the client side. In practice, only a small handful of apps will develop Autofill services because a device will only have one service as default at a time, and there is just a small number of 3rd-party apps providing these services (typically password managers). However, all apps targeting O with any autofillable fields should follow the necessary steps to 1) ensure their views can be autofilled and 2) optimize their autofill performance. Most of the time, there is little to no extra code involved, but the use of custom views and views with virtual child views requires more work.

The sample's Autofill service is implemented to parse the client's view hierarchy in search of autofillable fields that it has data for. If such fields exist in the hierarchy, the service sends data suggestions to the client to autofill those fields. The client uses the following attributes to specify autofill properties: importantForAutofill, autofillHints, and autofillType. importantForAutofill specifies whether the view is autofillable. autofillHints is a list of strings that hint to the service what data to fill the view with. This sample service only supports the hints listed here with the prefix AUTOFILL_HINT_*. autofillType tells the service the type of data it expects to receive (i.e. a list index, a date, or a string). Specifying autofillType is only necessary when implementing a custom view since all of the provided widgets in the UI toolkit do this for you.

To set the device's default Autofill service to the one in the sample, edit Settings > System > Languages & Input > Advanced > Auto-fill service and select the sample app. To edit the service's settings, tap the settings icon next to the Auto-fill service list item or open the Autofill Settings launcher icon.. Here, you can set whether you want to enable authentication on the entire autofill Response or just on individual autofill datasets. You should also set the master password to “unlock” authenticated autofill data with.

Note: This sample service stores all autofill data in SharedPreferences and thus is not secure. Be careful about what you store when experimenting with the sample because anyone with root access to your device will be able to view your autofill data.

The client side of the app has three Activities that each have autofillable fields. The first Activity uses standard views to comprise a login form. Very little needs to be done by the client app to ensure the views get autofilled properly. The second Activity uses a custom view with virtual children, meaning some autofillable child views are not known to the View hierarchy to be child views. Supporting autofill on these child views is a little more involved.

The following code snippet shows how to signal to the autofill service that a specific autofillable virtual view has come into focus:

class CustomVirtualView {
    // Cache AutofillManager system service
    mAutofillManager = context.getSystemService(AutofillManager.class);
    // Notify service which virtual view has come into focus.
    mAutofillManager.notifyViewEntered(CustomVirtualView.this, id, absBounds);
   // Notify service that a virtual view has left focus.
   mAutofillManager.notifyViewExited(CustomVirtualView.this, id);

Now that the autofillable view has signaled to the service that it has been autofilled, it needs to provide the virtual view hierarchy to the Autofill service. This is done out of the box for views part of the UI toolkit, but you need to implement this yourself if you have the view has virtual child views. The following code example shows the View method you have to override in order to provide this view hierarchy data to the Autofill service.

public void onProvideAutofillVirtualStructure(ViewStructure structure, int flags) {
    // Build a ViewStructure that will get passed to the AutofillService by the framework
    // when it is time to find autofill suggestions.
    int childrenSize = mItems.size();
    int index = structure.addChildCount(childrenSize);
    // Traverse through the view hierarchy, including virtual child views. For each view, we
    // need to set the relevant autofill metadata and add it to the ViewStructure.
    for (int i = 0; i < childrenSize; i++) {
        Item item = mItems.valueAt(i);
        ViewStructure child = structure.newChild(index);
        child.setId(, getContext().getPackageName(), null, item.line.idEntry);

After the service processes the Autofill request and sends back a series of Autofill Datasets (wrapped in a Response object), the user can pick which Dataset they want to autofill their views with. When a Dataset is selected, this method is invoked for all of the views that were associated with that Dataset by the service. For example, the Dataset might contain Autofill values for username, password, birthday, and address. This method would then be invoked on all four of those fields. The following code example shows how the sample app implements the method to deliver a UI update to the appropriate child view after the user makes their selection.

public void autofill(SparseArray<AutofillValue> values) {
    // User has just selected a Dataset from the list of autofill suggestions.
    // The Dataset is comprised of a list of AutofillValues, with each AutofillValue meant
    // to fill a specific autofillable view. Now we have to update the UI based on the
    // AutofillValues in the list.
    for (int i = 0; i < values.size(); i++) {
        final int id = values.keyAt(i);
        final AutofillValue value = values.valueAt(i);
        final Item item = mItems.get(id);
        if (item != null && item.editable) {
            // Set the item's text to the text wrapped in the AutofillValue.
            item.text = value.getTextValue();
        } else if (item == null) {
            // Component not found, so no-op.
        } else {
            // Component not editable, so no-op.


  • Android SDK 26
  • Android Build Tools v28.0.3
  • Android Support Repository


Screenshot Screenshot Screenshot Screenshot Screenshot Screenshot Screenshot Screenshot Screenshot Screenshot Screenshot

Getting Started

This sample uses the Gradle build system. To build this project, use the "gradlew build" command or use "Import Project" in Android Studio.


If you've found an error in this sample, please file an issue:

Patches are encouraged, and may be submitted by forking this project and submitting a pull request through GitHub. Please see for more details.

You can’t perform that action at this time.