Autofill (app side and service side)
Lets the keyboard offer saved usernames, passwords, cards and addresses in app forms.
In one line
Can offer saved logins, cards and addresses in forms, only after you tap a suggestion
Lets the keyboard offer saved usernames, passwords, cards and addresses in app forms.
The autofill service sees which fields the app shows (labels, IDs) and can fill them. Legacy Android services read the whole view tree.
What it can and can't do
What the user does: You tap a username, password, card or address field and choose a suggestion
It can
- Mark form fields so the keyboard knows to suggest a saved username or password
- Receive the value you choose from the suggestion
- Offer one time text message codes above the keyboard on iPhone
- Act as the autofill service itself if you pick the app in Settings
It cannot
- See your saved passwords or cards without you tapping a suggestion
- Fill fields with no action from you
- Pick itself as your password manager; you choose that in Settings
- Grab data for sites or apps the manager does not match
How it differs between platforms: Android lets you pick an autofill service in Settings. iPhone uses its own keychain or a password manager you enable.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Supported |
| First version | Android 8.0 (API 26) | iOS 12.0 |
| Permission or entitlement | BIND_AUTOFILL_SERVICE (service side) | NSContactsUsageDescription not needed; textContentType keys; Associated Domains for credentials |
| Protection level | signature | none |
| How access is granted | settings | none |
| What the user sees | User must pick the Autofill service in Settings | Quick Type bar suggestions |
| How long it lasts | Until changed | n/a |
| How to take it back | Settings > Passwords & accounts > Autofill service | Settings > Passwords > AutoFill Passwords |
| Store policy | None listed | None listed |
| API | AutofillService, View.setAutofillHints, AutofillManager | UITextContentType (.username, .password, .oneTimeCode), ASCredentialProviderViewController |
| Notes | Android 14 pushes passkeys and passwords through Credential Manager as well. | SMS one time codes can be offered above the keyboard in iOS 12 and later. |
Data you get
What comes back: Filled value
Shape: object
How often: per field
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
autofill hint | enum | id | username, password, creditCardNumber, postalAddress... | exact |
Technical limits
- Secure fields can be blocked from autofill by developers
The story
What it is
The keyboard can offer your saved logins, cards and addresses in app forms.
For you
You tap a login box and your saved username and password pop up above the keyboard. One tap fills it. You skip typing and avoid weak passwords.
For makers
Makers want sign up and checkout to be fast, because every extra typed field loses buyers. The password manager in the middle sees which fields an app shows, so its trust level matters.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | At checkout you tap the card box and your saved card and address fill in, so you buy before you change your mind. | Amazon, Shopify checkout |
| rideshare | An Uber login screen fills your email and password with one tap on a new phone. | Uber |
| delivery | A food delivery app fills your home address and phone so a hungry order takes seconds. | DoorDash |
| banking | A bank app fills a saved username while keeping the password behind a Face ID check. | None named |
| games | A game store login fills your account details so you can start playing after a reinstall. | Epic Games, Roblox |
| security | An attacker shows a fake login box in the hope the autofill service fills it, which is why good managers check the app identity first. | None named |
Risks
- Fake app can trick filling
- Service sees field labels
Android and iPhone in short
- Android: Android lets you pick any autofill service, and older ones could read the whole screen layout.
- iPhone: iPhone autofill is built into the keyboard and password manager, and apps only see what you choose to fill.
What the platform says
- Apple: AutoFill. Passwords, cards and codes appear above the keyboard so you can fill a form with one tap.
- Google: Autofill with Google. Android fills in saved passwords, addresses and payment details across apps from one place.
Good uses and abuse
Legitimate uses
- Password managers
Known abuse
- Malicious autofill service
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 4 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 2 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
History
- 2017-08, Android 8.0 (API 26): Autofill framework
- 2018-09, iPhone iOS 12: Password AutoFill and one time code fill
Related capabilities
Related
- Credential provider role (third party password and passkey manager). Can act as your phone's password and passkey manager once you turn it on
- Passkeys in an app (create and sign in). Can create and use passkeys inside the app after you approve with your device lock
Same idea on the web
- Autofill and autocomplete tokens. Can ask your browser to fill saved name, email, phone and address
- Browser saved address and card autofill. Can offer your saved addresses and cards to fill a form, if you pick them
Sources
How well checked: Based on official documentation.