How does designing custom android DPC app relate to Android management API?

Question

I\'m new to android enterprise development world, and I have some misconception of how different pieces in the android enterprise ecosystem relate to one another. Let me exp

Answer 1

https://developer.android.com/work/dpc/build-dpc

Caution: Android Enterprise is no longer accepting new registrations for custom device policy controllers (DPCs). Learn more.

Hi @Fred,

I found this above information from the mentioned path. I have some questions regarding the above conversation.

1. If we use Android management API to develop EMM, we don't need to implement Custom DPC app?

2. Whether we can register a account in EMM community with Custom DPC app?

3. Is it possible to use a custom DPC app with Android management API?

Answer 2

There are two distinct ways of managing Android devices:

The new way: the Android Management API. It is the way recommended by Google and it's significantly simpler than the old way, you don't need to call other APIs or to create a custom DPC. If your use case is not addressed by this API you can send feedback to Google so they can add the missing features.

The old way (no longer available for new deployments as of 2019-12-20): using custom DPC. For that you need to:

• create a custom DPC,
• register your custom DPC with Google by joining the EMM Community (this is how you get the afw#DPC_NAME),
• use the Google Play EMM API to install apps.

In the documentation you - the developer using these APIs - are referred as "the EMM". "EMM server" refers to the server that you own and that calls these API, and "EMM console" refers to the UI console that you expose to your IT admins, if any.