# Release your solution

By joining the EMM Provider Community, EMM developers that would like to release
solutions to their customers will be able to find support resources and have
their solutions validated and listed in the [Android Enterprise EMM Solutions
Directory](https://androidenterprisepartners.withgoogle.com/emm/). For detailed
information on the usage guidelines for an Android management solution, review
the [Permissible Usage guidelines](https://developers.google.com/android/management/permissible-usage).

## EMM solution validation

To build a solution using the Android Management API and submit it for
validation as it is ready for general availability, follow the following steps.
![launch-production-solution](https://developers.google.com/static/android/work/images/am-option-2.png)

### 1. Try the quickstart guide

Follow Android Management API [quickstart guide](https://developers.google.com/android/management/quickstart)
to 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 the
[Android Enterprise EMM Provider community](https://developers.google.com/android/management/join). This
closed community gives members access to service advisories, feature
announcements, and other updates. Members can also post questions within the
community 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, called
**solution sets**.

To [pass product review](https://developers.google.com/android/work/release-solution?api=clouddpx#4_pass_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's
[Enterprise Solutions Directory](https://androidenterprisepartners.withgoogle.com/emm/)
as offering a *Standard 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's
[Enterprise Solutions Directory](https://androidenterprisepartners.withgoogle.com/emm/)
as offering an *Advanced Management Set*.

|---|---|---|
| **Solution set** | **Android version** | **[Use case](https://developers.google.com/overview#enterprise_use_cases)** |
| [Work profile on personally-owned device](https://developers.google.com/android/work/requirements/work-profile) | 5.1+ | Employee-owned devices |
| [Work profile on company-owned device](https://developers.google.com/android/work/requirements/work-profile-corporate) | 8.0+ | Company-owned devices for work and personal use |
| [Fully managed device](https://developers.google.com/android/work/requirements/fully-managed-device) | 6.0+ | Company-owned devices work use only |
| [Dedicated device](https://developers.google.com/android/work/requirements/dedicated-device) | 6.0+ | Company-owned dedicated or shared-use devices |

To view a complete list of all Android Enterprise features, see the [feature
list](https://developers.google.com/android/work/requirements).

### 4. Pass product review

> [!IMPORTANT]
> **Key Point:** EMM solutions that pass product review are listed in the [Android
> Business Partners
> directory](https://androidenterprisepartners.withgoogle.com/#!/results/browse-all/0) .

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

#### Maintain compatibility

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

### 5. Deploy your solution

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

- This production launch must be made available to all prospective and current customers to purchase and deploy.
- The mandatory features for the chosen solution set must be available to customers.