AI-generated Key Takeaways
-
Android Enterprise has stopped accepting new registrations for custom device policy controllers (DPCs) using the Google Play EMM API.
-
New EMM solutions should now use the Android Management API, which includes a Google-provided DPC called Android Device Policy.
-
The Android Management API offers comprehensive device and app management and reduces development effort by eliminating the need for custom DPCs.
-
Existing EMMs with validated custom DPCs using the Google Play EMM API will continue to be supported.
Android Enterprise is no longer accepting new registrations for custom device policy controllers (DPC) using the Google Play EMM API. All new EMM solutions should now use Android Management API, which comes with its own DPC provided by Google.
For information on how to build a public solution using the Android Management API, see Develop your solution and Release your solution.
About Android Management API
Android Management API offers Android's full range of device and app management capabilities. Its companion DPC, Android Device Policy, is provided and maintained by Google. Android Device Policy automatically handles on-device policy enforcement set by the API.
This solution eliminates the need for EMM developers to create, update, and maintain their own custom DPC, and significantly reduces the development effort required to integrate new features as they become available.
Continued support for Google Play EMM API
Android Enterprise remains committed to supporting the Google Play EMM API for existing EMM community members who already have a custom DPC with a validated solution set. However, we're no longer accepting new registrations for custom DPCs that use the Play EMM API.