1 <html devsite> 2 <head> 3 <title>Android Compatibility</title> 4 <meta name="project_path" value="/_project.yaml" /> 5 <meta name="book_path" value="/_book.yaml" /> 6 </head> 7 <body> 8 <!-- 9 Copyright 2017 The Android Open Source Project 10 11 Licensed under the Apache License, Version 2.0 (the "License"); 12 you may not use this file except in compliance with the License. 13 You may obtain a copy of the License at 14 15 http://www.apache.org/licenses/LICENSE-2.0 16 17 Unless required by applicable law or agreed to in writing, software 18 distributed under the License is distributed on an "AS IS" BASIS, 19 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 20 See the License for the specific language governing permissions and 21 limitations under the License. 22 --> 23 24 25 26 <p>Android's purpose is to establish an open platform for developers to build 27 innovative apps.</p> 28 <ul> 29 <li>The Android Compatibility program defines technical details of the 30 Android platform and provides tools for OEMs to ensure developer applications 31 run on a variety of devices.</li> 32 <li>The Android SDK provides built-in tools for developers to clearly state the 33 device features required by their applications. 34 <li>Google Play shows applications only to those devices that can properly run 35 those applications.</li></li> 36 37 <h2 id="why-build-compatible-android-devices">Why build compatible Android 38 devices?</h2> 39 40 <h3 id="users-want-a-customizable-device">Users want customizable devices</h3> 41 42 <div class="attempt-right"> 43 <img src="images/compat-ecosystem.png" alt="Compatibility ecosystem" id="figure1" /> 44 <p class="img-caption"> 45 <strong>Figure 1.</strong> The Android ecosystem thrives with device compatibility 46 </p> 47 </div> 48 49 <p>A mobile phone is a highly personal, always-on, always-present gateway to 50 the Internet. We haven't met a user yet who didn't want to customize it by 51 extending its functionality. That's why Android was designed as a robust 52 platform for running aftermarket applications.</p> 53 54 <h3 id="developers-outnumber-us-all">Developers outnumber us all</h3> 55 <p>No device manufacturer can write all the software a user could conceivably 56 need. We need third-party developers to write the apps users want, so the 57 Android Open Source Project (AOSP) aims to make application development as easy 58 and open as possible.</p> 59 60 <h3 id="everyone-needs-a-common-ecosystem">Everyone needs a common ecosystem</h3> 61 <p>Every line of code developers write to work around a bug is a line of code 62 that didn't add a new feature. The more compatible mobile devices are, the more 63 applications we'll have to run on those devices. By building a fully compatible 64 Android device, you benefit from the huge pool of apps written for Android while 65 increasing the incentive for developers to build more apps.</p> 66 67 <h2 id="android-compatibility-is-free-and-its-easy">Android compatibility is 68 free, and it's easy</h2> 69 <p>To build an Android-compatible mobile device, follow this three-step 70 process:</p> 71 <ol> 72 <li><em>Obtain the <a href="/source/index.html">Android software source 73 code</a></em>. This is the source code for the Android platform that you port 74 to your hardware.</li> 75 <li><em>Comply with the Android Compatibility Definition Document (CDD)</em> 76 (<a href="/compatibility/android-cdd.pdf">PDF</a>, <a 77 href="/compatibility/android-cdd.html">HTML</a>). The CDD enumerates 78 the software and hardware requirements of a compatible Android device.</li> 79 <li><em>Pass the <a href="/compatibility/cts/">Compatibility 80 Test Suite (CTS)</a></em>. Use the CTS as an ongoing aid to evaluate 81 compatibility during the development process.</li> </ol> 82 83 <p>After complying with the CDD and passing the CTS, your device is Android 84 compatible, meaning Android apps in the ecosystem provide a consistent 85 experience when running on your device. For details about the Android 86 compatibility program, see the <a href="overview.html">program overview</a>.</p> 87 88 <h2 id="licensing-gms">Licensing Google Mobile Services (GMS)</h2> 89 <p>After building an Android compatible device, consider licensing Google Mobile 90 Services (GMS), Googles proprietary suite of apps (Google Play, YouTube, Google 91 Maps, Gmail, and more ) that run on top of Android. GMS is not part of the 92 Android Open Source Project and is available only through a license with Google. 93 For information on how to request a GMS license, see 94 <a href="contact-us.html">Contact Us</a>.</p> 95 96 </body> 97 </html> 98
