[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-07-26 UTC。"],[],[],null,["# Android Compatibility program overview\n\nAn *Android-compatible device* is any device that can run any\nthird-party app written by third-party developers using the Android SDK and NDK.\nAn Android-compatible device must adhere to the\nrequirements of the compatibility definition document (CDD), and pass the\ncompatibility test suite (CTS). Android-compatible devices are eligible to\nparticipate in the Android ecosystem which includes potential licensure of the\nAndroid Play Store and the Google Mobile Services (GMS) suite\nof applications, and use of the Android trademark. Anyone is welcome to use the\nAndroid source code, but to be considered part of the Android ecosystem, your\ndevice must be Android-compatible.\n\nThis document provides an overview of the *Android Compatibility program*\nwhich represents the processes, requirements, and tests used to ensure that your\ndevice is Android-compatible.\n\nReasons to build compatible Android\ndevices\n-------------------------------------------\n\n### Users want customizable devices\n\n\n**Figure 1.** The Android ecosystem thrives with device compatibility\n\nA mobile phone is a highly personal, always-on, always-present gateway to\nthe Internet. We haven't met a user yet who didn't want to customize it by\nextending its functionality. That's why Android was designed as a robust\nplatform for running aftermarket apps.\n\n### Developers outnumber us all\n\nNo device manufacturer can write all the software a user could conceivably\nneed. We need third-party developers to write the apps users want, so the\nAndroid Open Source Project (AOSP) aims to make app development as easy\nand open as possible.\n\n### Everyone needs a common ecosystem\n\nEvery line of code developers write to work around a bug is a line of code\nthat didn't add a new feature. The more compatible mobile devices are, the more\napps we'll have to run on those devices. By building a fully compatible\nAndroid device, you benefit from the huge pool of apps written for Android while\nincreasing the incentive for developers to build more apps.\n\nProgram goals\n-------------\n\nThe Android compatibility program works for the benefit of the entire\nAndroid community, including users, developers, and device manufacturers.\n\nEach group depends on the others. Users want a wide selection of devices\nand great apps; great apps come from developers motivated by a large market\nfor their apps with many devices in users' hands; device manufacturers rely\non a wide variety of great apps to increase their products' value for\nconsumers.\n\nOur goals were designed to benefit each of these groups:\n\n- *Provide a consistent app and hardware environment to app\n developers.*\n Without a strong compatibility standard, devices can vary so\n greatly that developers must design different versions of their apps\n for different devices. The compatibility program provides a precise definition\n of what developers can expect from a compatible device in terms of APIs and\n capabilities. Developers can use this information to make good design\n decisions, and be confident that their apps will run well on any compatible\n device.\n\n- *Enable a consistent app experience for consumers.*\n If an app runs well on one compatible Android device, it should run well on\n any other device that is compatible with the same Android platform version.\n Android devices will differ in hardware and software capabilities, so the\n compatibility program also provides the tools needed for distribution systems\n such as Google Play to implement appropriate filtering. This means\n users see only the apps they can actually run.\n\n- *Enable device manufacturers to differentiate while being\n compatible.*\n The Android compatibility program focuses on the aspects of\n Android relevant to running third-party apps, which allows device\n manufacturers the flexibility to create unique devices that are nonetheless\n compatible.\n\n- *Minimize costs and overhead associated with compatibility.*\n Ensuring compatibility should be easy and inexpensive to\n device manufacturers. The testing tool is free, open source, and\n available for [download](/docs/compatibility/cts/downloads).\n It is designed to be used for continuous self-testing\n during the device development process to eliminate the cost of changing your\n workflow or sending your device to a third party for testing. Meanwhile, there\n are no required certifications, and thus no corresponding costs and\n fees.\n\nBuild an Android-compatible device\n----------------------------------\n\nTo build an Android-compatible mobile device, follow this three-step\nprocess:\n\n1. Using [AOSP](/docs/setup), implement Android on your device.\n2. Ensure your device complies with the [Android Compatibility Definition Document](/docs/compatibility/cdd). The CDD enumerates the software and hardware requirements for an Android-compatible device.\n3. Pass the [Compatibility\n Test Suite (CTS)](/docs/compatibility/cts). Use the CTS as an ongoing aid to evaluate compatibility during the development process.\n\nAfter achieving compatibility, your device is considered Android compatible and you can consider\n[Licensing Google Mobile\nServices (GMS)](/docs/setup/community#for-business-inquiries) and prepare to use the Android trademark. For brand guidelines, refer to the\nAndroid section of the\n[Partner Marketing\nHub](https://partnermarketinghub.withgoogle.com/brands/android/overview/brand-introduction/).\n\n| **Note:** Just as each version of the Android platform exists in a separate branch in the source code tree, there is a separate CTS and CDD for each version as well. The CDD, CTS, and source code are --- along with your hardware and your software customizations --- everything you need to create a compatible device."]]