blob: 6b29fa3a2c2bd4d13f029e365ea3934105ac64db [file] [log] [blame]
Robert Ly35f2fda2013-01-29 16:27:05 -08001page.title=Android Compatibility
2@jd:body
3
4<!--
Heidi von Markham06c50bf2015-05-14 12:21:57 -07005 Copyright 2015 The Android Open Source Project
Robert Ly35f2fda2013-01-29 16:27:05 -08006
Heidi von Markham06c50bf2015-05-14 12:21:57 -07007 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
Robert Ly35f2fda2013-01-29 16:27:05 -080010
11 http://www.apache.org/licenses/LICENSE-2.0
12
Heidi von Markham06c50bf2015-05-14 12:21:57 -070013 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.
Robert Ly35f2fda2013-01-29 16:27:05 -080018-->
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
Heidi von Markham06c50bf2015-05-14 12:21:57 -070027<p>Android's purpose is to establish an open platform for developers to build
28innovative apps.</p>
29<ul>
30<li>The Android Compatibility program defines technical details of the
31Android platform and provides tools for OEMs to ensure developer applications
32run on a variety of devices.</li>
33<li>The Android SDK provides built-in tools for developers to clearly state the
34device features requires by their applications.
35<li>Google Play shows applications only to those devices that can properly run
36those applications.</li></li>
Robert Ly35f2fda2013-01-29 16:27:05 -080037
Heidi von Markham06c50bf2015-05-14 12:21:57 -070038<h2 id="why-build-compatible-android-devices">Why build compatible Android
39devices?</h2>
40
41<h3 id="users-want-a-customizable-device">Users want customizable devices</h3>
Clay Murphy468ba572015-04-13 18:25:11 -070042
43<div class="figure">
44 <img src="images/compat-ecosystem.png" alt="Compatibility ecosystem" id="figure1" />
45 <p class="img-caption">
Heidi von Markham06c50bf2015-05-14 12:21:57 -070046 <strong>Figure 1.</strong> The Android ecosystem thrives with device compatibility
Clay Murphy468ba572015-04-13 18:25:11 -070047 </p>
48</div>
49
Robert Ly35f2fda2013-01-29 16:27:05 -080050<p>A mobile phone is a highly personal, always-on, always-present gateway to
51the Internet. We haven't met a user yet who didn't want to customize it by
52extending its functionality. That's why Android was designed as a robust
Clay Murphy710b6652014-01-06 16:04:37 -080053platform for running aftermarket applications.</p>
Heidi von Markham06c50bf2015-05-14 12:21:57 -070054
55<h3 id="developers-outnumber-us-all">Developers outnumber us all</h3>
56<p>No device manufacturer can write all the software a user could conceivably
57need. We need third-party developers to write the apps users want, so the
58Android Open Source Project (AOSP) aims to make application development as easy
59and open as possible.</p>
60
61<h3 id="everyone-needs-a-common-ecosystem">Everyone needs a common ecosystem</h3>
62<p>Every line of code developers write to work around a bug is a line of code
63that didn't add a new feature. The more compatible mobile devices are, the more
64applications we'll have to run on those devices. By building a fully compatible
65Android device, you benefit from the huge pool of apps written for Android while
66increasing the incentive for developers to build more apps.</p>
67
68<h2 id="android-compatibility-is-free-and-its-easy">Android compatibility is
69free, and it's easy</h2>
70<p>To build an Android-compatible mobile device, follow this three-step
71process:</p>
Robert Ly35f2fda2013-01-29 16:27:05 -080072<ol>
Heidi von Markham06c50bf2015-05-14 12:21:57 -070073<li><em>Obtain the <a href="{@docRoot}source/index.html">Android software source
74code</a></em>. This is the source code for the Android platform that you port
75to your hardware.</li>
76<li><em>Comply with the <a href="{@docRoot}compatibility/android-cdd.pdf">Android
77Compatibility Definition Document (CDD)</a></em>. The CDD enumerates the
78software and hardware requirements of a compatible Android device.</li>
79<li><em>Pass the <a href="{@docRoot}compatibility/cts-intro.html">Compatibility
80Test Suite (CTS)</a></em>. Use the CTS as an ongoing aid to evaluate
81compatibility during the development process.</li>
Robert Ly35f2fda2013-01-29 16:27:05 -080082</ol>
83
Heidi von Markham06c50bf2015-05-14 12:21:57 -070084<p>After complying with the CDD and passing the CTS, your device is Android
85compatible, meaning Android apps in the ecosystem provide a consistent
86experience when running on your device. For details about the Android
87compatibility program, see the <a href="overview.html">program overview</a>.</p>
Clay Murphyb59afd72015-01-30 11:16:20 -080088
Heidi von Markham06c50bf2015-05-14 12:21:57 -070089<h2 id="licensing-gms">Licensing Google Mobile Services (GMS)</h2>
90<p>After building an Android compatible device, consider licensing Google Mobile
91Services (GMS), Google’s proprietary suite of apps (Google Play, YouTube, Google
92Maps, Gmail, and more ) that run on top of Android. GMS is not part of the
93Android Open Source Project and is available only through a license with Google.
94For information on how to request a GMS license, see
95<a href="contact-us.html">Contact Us</a>.</p>