# Develop your solution

This page provides a brief summary of how to use
[Android Management API](https://developers.google.com/android/management) as a foundation for developing an
enterprise mobility management (EMM) solution for Android.

|---|---|
| **Development effort** | **EMM console:** API integration, front-end development |
| **[Enterprise types](https://developers.google.com/android/work/overview#customer_onboarding)** | Managed Google Play Accounts enterprises |
| **[Use cases](https://developers.google.com/android/work/overview#android_devices_enterprise_use_cases)** | Work profile devices Fully managed devices Dedicated devices |
| **Minimum Android version** | Android 5.1 |

![](https://developers.google.com/static/android/work/images/android-management-api.png) **Figure 1.** Android Device Policy automatically handles communication between your EMM console and managed devices

The Android Management API supports mobile device management (MDM) and mobile
application management (MAM). The API's partner app, [Android Device Policy](https://play.google.com/store/apps/details?id=com.google.android.apps.work.clouddpc), receives management policy settings
from the API and enforces them on devices.

## Set up devices for management

![](https://developers.google.com/static/android/management/images/enrollment-token.png) **Figure 2.** Provision devices with an enrollment token

The Android Management API uses [enrollment tokens](https://developers.google.com/android/management/reference/rest/v1/enterprises.enrollmentTokens)
to bind devices with an enterprise. Passing an enrollment token to a device
initiates provisioning, a process that also includes installing Android Device
Policy and adding a managed Google Play account to the device.

A successfully provisioned device is represented by a `Devices` resource. For
more information, see [Enroll and provision a
device](https://developers.google.com/android/management/provision-device).

## Manage devices and distribute apps with policies

The Android Management API's `Policies` resource allows you to configure and
save unique groups of enterprise management settings. IT admins still use
managed Google Play to discover apps manage app permissions, but can distribute
apps by adding them to policies.

You can use `Policies` to manage the full range of Android Enterprise device
deployments. For example, to manage **devices for knowledge workers**, you
could create a policy that:

- Enforces minimum password requirements.
- Remotely installs apps or makes apps available in managed Google Play.
- Specifies a maintenance window for system updates.

To manage **company-owned devices for dedicated or shared use**, you could
create a policy that:

- Locks down a device to a single app or sets of apps.
- Disables features such as camera, notifications, and location mode.

> [!IMPORTANT]
> **Key Point:** With Android Management API's policy-based model, you can integrate new policy settings into your EMM console with minimal development effort. This includes new policy settings for the latest versions of Android as they're released.

When you associate a policy with a device, the API automatically sends
the policy settings to Android Device Policy on the specified device or the
specified user's device(s). After Android Device Policy receives the settings,
it automatically enforces them on the device.

A complete list of policy settings is available in the [Android Management API
reference](https://developers.google.com/android/management/reference/rest/v1/enterprises.policies).

## Get started with the Android Management API

1. Review the steps required to [release your solution](https://developers.google.com/android/work/release-solution).
2. Review the [Android Management API developer documentation](https://developers.google.com/android/management).

*** ** * ** ***

**Next:** [Release your solution](https://developers.google.com/android/work/release-solution)