Page Summary

outlined_flag

• EMM developers can join the EMM Provider Community for support and to have their solutions validated and listed.

• To get an EMM solution validated, follow a process that includes trying a quickstart guide, joining the EMM Provider community, developing the solution to support at least one solution set, passing product review, and deploying the solution.

• EMM solutions must support a minimum set of features organized into four solution sets based on use cases and Android versions.

• Passing product review is required to be listed in the Android Business Partners directory, and approved EMMs must maintain compatibility with feature requirement changes.

• After passing product review, approved EMMs must deploy their solution publicly to all prospective and current customers, making the mandatory features available.

By joining the EMM Provider Community, EMM developers that would like to releasesolutions to their customers will be able to find support resources and havetheir solutions validated and listed in theAndroid Enterprise EMM SolutionsDirectory. For detailedinformation on the usage guidelines for an Android management solution, reviewthePermissible Usage guidelines.

EMM solution validation

To build a solution using the Android Management API and submit it forvalidation as it is ready for general availability, follow the following steps.

1. Try the quickstart guide

Follow Android Management APIquickstart guideto become familiar with API usage and implementation.

2. Join Android Enterprise EMM Provider community

The first step to releasing a public Android EMM solution is to join theAndroid Enterprise EMM Provider community. Thisclosed community gives members access to service advisories, featureannouncements, and other updates. Members can also post questions within thecommunity and receive direct support from Google.

3. Develop your solution

The Android EMM solution you develop must support a minimum set of features.Android Enterprise features are organized into four distinct use cases, calledsolution sets.

Topass product review, your solution must support the standard features of at least one solution set.Solutions that pass standard feature verification are listed in Android'sEnterprise Solutions Directoryas offering aStandard Management Set.

For each solution set, you can optionally support a set of advanced features.Solutions that pass advanced feature verification are listed in Android'sEnterprise Solutions Directoryas offering anAdvanced Management Set.

Solution set	Android version	Use case
Work profile on personally-owned device	5.1+	Employee-owned devices
Work profile on company-owned device	8.0+	Company-owned devices for work and personal use
Fully managed device	6.0+	Company-owned devices work use only
Dedicated device	6.0+	Company-owned dedicated or shared-use devices

To view a complete list of all Android Enterprise features, see thefeaturelist.

4. Pass product review

Key Point: EMM solutions that pass product review are listed in theAndroidBusiness Partnersdirectory.

After successfully registering with Google's EMM Community, EMMs have 180 daysto develop their solution, pass a product review, and deploy their solutionpublicly. The product review validates whether the EMM's solution meets therequirements of at least one solution set.

Maintain compatibility

Feature requirements are subject to change at any time. When changes arepublished, approved EMMs must implement any resulting changes within 180 days toretain access to Android Enterprise's services.

5. Deploy your solution

After passing product review, EMMs must make the features of their approvedsolution sets available to customers as a cloud-based and-or on-premisessolution.

• This production launch must be made available to all prospective and currentcustomers to purchase and deploy.
• The mandatory features for the chosen solution set must be available tocustomers.