Android Management API를 사용하여 솔루션을 빌드하고 정식 버전 출시 준비가 되면 검증을 위해 제출하려면 다음 단계를 따르세요.
1. 빠른 시작 가이드 사용해 보기
Android Management API 빠른 시작 가이드에 따라 API 사용 및 구현에 익숙해지세요.
2. Android Enterprise EMM 공급자 커뮤니티 가입
공개 Android EMM 솔루션을 출시하려면 먼저 Android Enterprise EMM 제공업체 커뮤니티에 가입해야 합니다. 이 비공개 커뮤니티는 회원에게 서비스 권고, 기능 공지사항, 기타 업데이트를 제공합니다. 회원은 커뮤니티 내에서 질문을 게시하고 Google의 직접적인 지원을 받을 수도 있습니다.
3. 솔루션 개발
개발하는 Android EMM 솔루션은 최소한의 기능을 지원해야 합니다.
Android Enterprise 기능은 솔루션 세트라고 하는 네 가지 고유한 사용 사례로 구성됩니다.
제품 검토를 통과하려면 솔루션이 하나 이상의 솔루션 세트의 표준 기능을 지원해야 합니다.
표준 기능 인증을 통과한 솔루션은 Android의 엔터프라이즈 솔루션 디렉터리에 표준 관리 세트를 제공하는 것으로 나열됩니다.
각 솔루션 세트의 경우 원하는 경우 고급 기능 집합을 지원할 수 있습니다.
고급 기능 인증을 통과한 솔루션은 Android의 엔터프라이즈 솔루션 디렉터리에 고급 관리 세트를 제공하는 것으로 나열되어 있습니다.
[null,null,["최종 업데이트: 2025-08-31(UTC)"],[[["\u003cp\u003eEMM developers can join the EMM Provider Community for support, validation, and listing in the Android Enterprise Solutions Directory.\u003c/p\u003e\n"],["\u003cp\u003eTo release an EMM solution, developers need to join the community, develop their solution supporting a minimum set of features, pass a product review, and deploy the solution publicly.\u003c/p\u003e\n"],["\u003cp\u003eSolutions must support at least one of the four solution sets: Work profile on personally-owned devices, Work profile on company-owned devices, Fully managed devices, or Dedicated devices.\u003c/p\u003e\n"],["\u003cp\u003eAfter registering with Google's EMM Community, EMMs have 180 days to develop, pass product review, and deploy their solution publicly.\u003c/p\u003e\n"],["\u003cp\u003eApproved EMM solutions must maintain compatibility with feature requirements and implement any published changes within 180 days to retain access to Android Enterprise services.\u003c/p\u003e\n"]]],[],null,["# Release your solution\n\nBy joining the EMM Provider Community, EMM developers that would like to release\nsolutions to their customers will be able to find support resources and have\ntheir solutions validated and listed in the [Android Enterprise EMM Solutions\nDirectory](https://androidenterprisepartners.withgoogle.com/emm/). For detailed\ninformation on the usage guidelines for an Android management solution, review\nthe [Permissible Usage guidelines](/android/management/permissible-usage).\n\nEMM solution validation\n-----------------------\n\nTo build a solution using the Android Management API and submit it for\nvalidation as it is ready for general availability, follow the following steps.\n\n### 1. Try the quickstart guide\n\nFollow Android Management API [quickstart guide](/android/management/quickstart)\nto become familiar with API usage and implementation.\n\n### 2. Join Android Enterprise EMM Provider community\n\nThe first step to releasing a public Android EMM solution is to join the\n[Android Enterprise EMM Provider community](/android/management/join). This\nclosed community gives members access to service advisories, feature\nannouncements, and other updates. Members can also post questions within the\ncommunity and receive direct support from Google.\n\n### 3. Develop your solution\n\nThe Android EMM solution you develop must support a minimum set of features.\nAndroid Enterprise features are organized into four distinct use cases, called\n**solution sets**.\n\nTo [pass product review](/android/work/release-solution?api=clouddpx#4_pass_product_review)\n, your solution must support the standard features of at least one solution set.\nSolutions that pass standard feature verification are listed in Android's\n[Enterprise Solutions Directory](https://androidenterprisepartners.withgoogle.com/emm/)\nas offering a *Standard Management Set*.\n\nFor each solution set, you can optionally support a set of advanced features.\nSolutions that pass advanced feature verification are listed in Android's\n[Enterprise Solutions Directory](https://androidenterprisepartners.withgoogle.com/emm/)\nas offering an *Advanced Management Set*.\n\n|-------------------------------------------------------------------------------------------|---------------------|-------------------------------------------------|\n| **Solution set** | **Android version** | **[Use case](/overview#enterprise_use_cases)** |\n| [Work profile on personally-owned device](/android/work/requirements/work-profile) | 5.1+ | Employee-owned devices |\n| [Work profile on company-owned device](/android/work/requirements/work-profile-corporate) | 8.0+ | Company-owned devices for work and personal use |\n| [Fully managed device](/android/work/requirements/fully-managed-device) | 6.0+ | Company-owned devices work use only |\n| [Dedicated device](/android/work/requirements/dedicated-device) | 6.0+ | Company-owned dedicated or shared-use devices |\n\nTo view a complete list of all Android Enterprise features, see the [feature\nlist](/android/work/requirements).\n\n### 4. Pass product review\n\n| **Key Point:** EMM solutions that pass product review are listed in the [Android\n| Business Partners\n| directory](https://androidenterprisepartners.withgoogle.com/#!/results/browse-all/0) .\n\nAfter successfully registering with Google's EMM Community, EMMs have 180 days\nto develop their solution, pass a product review, and deploy their solution\npublicly. The product review validates whether the EMM's solution meets the\nrequirements of at least one solution set.\n\n#### Maintain compatibility\n\nFeature requirements are subject to change at any time. When changes are\npublished, approved EMMs must implement any resulting changes within 180 days to\nretain access to Android Enterprise's services.\n\n### 5. Deploy your solution\n\nAfter passing product review, EMMs must make the features of their approved\nsolution sets available to customers as a cloud-based and-or on-premises\nsolution.\n\n- This production launch must be made available to all prospective and current customers to purchase and deploy.\n- The mandatory features for the chosen solution set must be available to customers."]]
