Everyone likes it when you remember their name. One of the simplest, most effective things you can do to make your app more lovable is to remember who your user is—especially when the user upgrades to a new device or starts carrying a tablet as well as a phone. But how do you know who your user is? And how do you recognize them on a new device?
For many applications, the answer is the
AccountManager APIs. With the
user's permission, you can use Account Manager to fetch the account names
that the user has stored on their device.
Integration with the user's accounts allows you to do a variety of things such as:
- Auto-fill forms with the user's email address.
- Retrieve an ID that is tied to a user, not the device.
Determine if AccountManager is for you
Applications typically try to remember the user using one of three techniques:
- Ask the user to type in a username
- Retrieve a unique device ID to remember the device
- Retrieve a built-in account from
Option (a) is problematic. First, asking the user to type something before entering your app will automatically make your app less appealing. Second, there's no guarantee that the username chosen will be unique.
Option (b) is less onerous for the user, but it's tricky to get right. More importantly, it only allows you to remember the user on one device. Imagine the frustration of someone who upgrades to a shiny new device, only to find that your app no longer remembers them.
Option (c) is the preferred technique. Account Manager allows you to get information about the accounts that are stored on the user's device. As we'll see in this lesson, using Account Manager lets you remember your user, no matter how many devices the user may own, by adding just a couple of extra taps to your UI.
Decide what type of account to use
Android devices can store multiple accounts from many different providers.
When you query
AccountManager for account names, you can choose to filter
account type. The account type is a string that uniquely identifies the entity
that issued the account. For instance, Google accounts have type "com.google,"
while Twitter uses "com.twitter.android.auth.login."
Request GET_ACCOUNT permission
<manifest ... > <uses-permission android:name="android.permission.GET_ACCOUNTS" /> ... </manifest>
Inform users and get consent
If you get the list of user accounts by calling either
keep in mind that the API returns personal and sensitive user data. If your app
accesses, collects, uses, or shares personal and sensitive data, you must
clearly disclose that fact to users. For apps published on Google Play,
policies protecting user data require that you do the following:
- Disclose to the user how your app accesses, collects, uses, or shares personal and sensitive data. Learn more about acceptable disclosure and consent.
To learn more, visit the Google Play Policy regarding user data.
Query AccountManager for a list of accounts
Once you decide what account type you're interested in, you need to query for accounts of that
type. Get an instance of
AccountManager by calling
AccountManager.get(). Then use that
instance to call
val am: AccountManager = AccountManager.get(this) // "this" references the current Context val accounts: Array<out Account> = am.getAccountsByType("com.google")
AccountManager am = AccountManager.get(this); // "this" references the current Context Account accounts = am.getAccountsByType("com.google");
Use the account object to personalize your app
Account object contains
an account name, which for Google accounts is an email address. You can use this information in
several different ways, including the following:
- As suggestions in forms, so the user doesn't need to input account information by hand.
- As a key into your own online database of usage and personalization information.
Decide whether an account name is enough
An account name is a good way to remember the user, but the
itself doesn't protect your data or give you access to anything besides the user's account name. If your app
needs to allow the user to go online to access private data, you'll need something stronger: authentication.
The next lesson explains how to authenticate to existing online services. The lesson after that
deals with writing a custom authenticator so that you can install your own