Comparison of Android channels

Channel	What it is used for	Registration and boundaries
Aitera DPC	Corporate agent for managing a device through the Aitera channel.	For COBO/COPE scenarios, the wizard creates a QR for initial setup. The APK and its updates are managed in the DPC section. Compatibility and available commands depend on the mode and the agent version.
Google Android Enterprise / AMAPI	Device management through the Android Management API and the Android Device Policy app from Google.	An organization (enterprise), an enrollment token and Google policies are used. Android Device Policy is the only controller compatible with AMAPI. The Aitera APK does not replace the Google agent. For details, see Android Enterprise integration.
Mobile app / BYOD	Connecting a personal phone to the Aitera mobile app, including passing service addresses.	The mobile connection QR passes the addresses required by the app. By itself, it does not install Device Owner and does not create an Android work profile. Do not equate app registration with system-level MDM management.

AMAPI describes Google’s own sets of solutions, including personal devices with a work profile, corporate devices and fully managed devices. Specific Aitera capabilities should be verified on the screen, in the template and by the actual result on the device; the existence of a capability in the Google API does not mean it is available in this console. See the official description of the Android Management API.

Before you start, choose the channel and the device ownership model: corporate scenario or personal Android.