blob: 95a39dcffc5f72de48601e5833dc9787efc45770 [file] [log] [blame]
Robert Ly35f2fda2013-01-29 16:27:05 -08001page.title=Android Compatibility
2@jd:body
3
4<!--
Clay Murphyb59afd72015-01-30 11:16:20 -08005 Copyright 2015 The Android Open Source Project
Robert Ly35f2fda2013-01-29 16:27:05 -08006
7 Licensed under the Apache License, Version 2.0 (the "License");
8 you may not use this file except in compliance with the License.
9 You may obtain a copy of the License at
10
11 http://www.apache.org/licenses/LICENSE-2.0
12
13 Unless required by applicable law or agreed to in writing, software
14 distributed under the License is distributed on an "AS IS" BASIS,
15 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
16 See the License for the specific language governing permissions and
17 limitations under the License.
18-->
Clay Murphy468ba572015-04-13 18:25:11 -070019<div id="qv-wrapper">
20 <div id="qv">
21 <h2>In this document</h2>
22 <ol id="auto-toc">
23 </ol>
24 </div>
25</div>
Robert Ly35f2fda2013-01-29 16:27:05 -080026
27<p>Android's purpose is to establish an open platform for developers to build innovative apps.
Clay Murphy710b6652014-01-06 16:04:37 -080028The Android Compatibility program defines the technical details of the Android platform and provides
Robert Ly35f2fda2013-01-29 16:27:05 -080029tools used by OEMs to ensure that developers' apps run on a variety of devices. The Android SDK
30provides built-in tools that developers use to clearly state the device features their apps
31require. And Google Play shows apps only to those devices that can properly run them.
32</p>
33
34<h2 id="why-build-compatible-android-devices">Why build compatible Android devices?</h2>
Clay Murphy468ba572015-04-13 18:25:11 -070035
36<div class="figure">
37 <img src="images/compat-ecosystem.png" alt="Compatibility ecosystem" id="figure1" />
38 <p class="img-caption">
39 <strong>Figure 1.</strong> How the Android ecosystem thrives with device compatibility
40 </p>
41</div>
42
Robert Ly35f2fda2013-01-29 16:27:05 -080043<h3 id="users-want-a-customizable-device">Users want a customizable device.</h3>
44<p>A mobile phone is a highly personal, always-on, always-present gateway to
45the Internet. We haven't met a user yet who didn't want to customize it by
46extending its functionality. That's why Android was designed as a robust
Clay Murphy710b6652014-01-06 16:04:37 -080047platform for running aftermarket applications.</p>
Robert Ly35f2fda2013-01-29 16:27:05 -080048<h3 id="developers-outnumber-us-all">Developers outnumber us all.</h3>
49<p>No device manufacturer can hope to write all the software that a person could
Clay Murphy710b6652014-01-06 16:04:37 -080050conceivably need. We need third-party developers to write the apps users want;
Robert Ly35f2fda2013-01-29 16:27:05 -080051so the Android Open Source Project aims to make it as easy and open as
52possible for developers to build apps.</p>
53<h3 id="everyone-needs-a-common-ecosystem">Everyone needs a common ecosystem.</h3>
54<p>Every line of code developers write to work around a particular phone's bug
55is a line of code that didn't add a new feature. The more compatible phones
56there are, the more apps there will be. By building a fully compatible Android
57device, you benefit from the huge pool of apps written for Android, while
58increasing the incentive for developers to build more of those apps.</p>
59<h2 id="android-compatibility-is-free-and-its-easy">Android compatibility is free, and it's easy.</h2>
60<p>If you are building a mobile device, you can follow these steps to make
61sure your device is compatible with Android. For more details about the
62Android compatibility program in general, see <a href="overview.html">the program overview</a>.</p>
63<p>Building a compatible device is a three-step process:</p>
64<ol>
65<li>
Clay Murphy710b6652014-01-06 16:04:37 -080066<p><em>Obtain the <a href="{@docRoot}source/index.html">Android software source
67code</a></em>.
68 This is the source code for the Android platform that you port to your hardware.</p>
Robert Ly35f2fda2013-01-29 16:27:05 -080069</li>
70<li>
Clay Murphy710b6652014-01-06 16:04:37 -080071<p><em>Comply with the <a href="{@docRoot}compatibility/android-cdd.pdf">Android
72Compatibility Definition Document (CDD)</a></em>.
Robert Ly35f2fda2013-01-29 16:27:05 -080073 The CDD enumerates the software and hardware requirements of a compatible Android device.</p>
74</li>
75<li>
Clay Murphy710b6652014-01-06 16:04:37 -080076<p><em>Pass the <a href="{@docRoot}compatibility/cts-intro.html">Compatibility
77Test Suite (CTS)</a></em>.
78 Use the CTS as an ongoing aid to compatibility during the development process.</p>
Robert Ly35f2fda2013-01-29 16:27:05 -080079</li>
80</ol>
81
Clay Murphyb59afd72015-01-30 11:16:20 -080082<p>After complying with the CDD and passing the CTS, your device is now Android
83compatible. Android apps in the ecosystem will have a consistent experience on
84your device.</p>
85
86<h2 id="licensing-gms">Licensing Google Mobile Services</h2>
87<p>If you've built an Android compatible device, you may wish to inquire about
88licensing Google’s proprietary suite of apps that run on top of Android -
89Google Mobile Services (GMS, which include Google Play, YouTube, Google Maps,
90Gmail, and more). Google Mobile Services is not part of the Android Open Source
Clay Murphy468ba572015-04-13 18:25:11 -070091Project and is available only through a license with Google. Please visit
92<a href="contact-us.html">Contact Us</a> for more information on how to inquire
93about a GMS license.</p>