Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 1 | page.title=Android Compatibility |
Gaurav Mathur | 800158f | 2009-10-08 23:50:24 -0700 | [diff] [blame] | 2 | doc.type=compatibility |
| 3 | @jd:body |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 4 | <p>Android is an open source product, and anyone can use the source code to build |
| 5 | devices. Incautious implementations, however, can easily introduce bugs that |
| 6 | cause third-party applications to break. The purpose of the Android |
| 7 | Compatibility Program is to help Android device implementations remain |
| 8 | compatible with all apps.</p> |
| 9 | <h2>Why build compatible Android devices?</h2> |
| 10 | <h3>Users want a customizable device.</h3> |
| 11 | <p>A mobile phone is a highly personal, always-on, always-present gateway to |
| 12 | the Internet. We haven't met a user yet who didn't want to customize it by |
| 13 | extending its functionality. That's why Android was designed as a robust |
| 14 | platform for running after-market applications.</p> |
Gaurav Mathur | 800158f | 2009-10-08 23:50:24 -0700 | [diff] [blame] | 15 | |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 16 | <h3>Developers outnumber us all.</h3> |
| 17 | <p>No device manufacturer can hope to write all the software that anyone could |
| 18 | conceivably need. We need third-party developers to write the apps users want, |
| 19 | so the Android Open Source Project aims to make it as easy and open as |
| 20 | possible for developers to build apps.</p> |
Gaurav Mathur | 800158f | 2009-10-08 23:50:24 -0700 | [diff] [blame] | 21 | |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 22 | <h3>Everyone needs a common ecosystem.</h3> |
| 23 | <p>Every line of code developers write to work around a particular phone's bug |
| 24 | is a line of code that didn't add a new feature. The more compatible phones |
| 25 | there are, the more apps there will be. By building a fully compatible Android |
| 26 | device, you benefit from the huge pool of apps written for Android, while |
| 27 | increasing the incentive for developers to build more of those apps.</p> |
Gaurav Mathur | 800158f | 2009-10-08 23:50:24 -0700 | [diff] [blame] | 28 | |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 29 | |
| 30 | <h2>Android compatibility is free, and it's easy.</h2> |
| 31 | <p>If you are building a mobile device, you can follow these steps to make |
| 32 | sure your device is compatible with Android. For more details about the |
| 33 | Android compatibility program in general, see <a |
| 34 | href="{@docRoot}compatibility/overview.html">the program overview</a>.</p> |
| 35 | <p>Building a compatible device is a four-step process:</p> |
| 36 | <ol> |
| 37 | <li><b>Obtain the Android software stack source code</b><p>This is the |
| 38 | <a href="{@docRoot}source/index.html">source code for the Android |
| 39 | platform</a>, that you port to your hardware.</p></li> |
| 40 | <li><b>Comply with Android Compatibility Definition Document</b><p> |
| 41 | This document enumerates the software and the hardware features of |
| 42 | a compatible Android device.</p></li> |
| 43 | <li><b>Pass the Compatibility Test Suite (CTS)</b><p>You can use the CTS |
| 44 | as an ongoing aid to compatibility during the development process.</p></li> |
| 45 | <li><b>Submit CTS report</b><p>[Optional] You can also submit your CTS report, |
| 46 | so that it can be validated and recorded.</p><p><i>Note: |
| 47 | the submission system is currently under construciton, and is not currently |
| 48 | available.</i></p></li> |
| 49 | </ol> |
| 50 | |
| 51 | <h2>Benefits of compatibility</h2> |
| 52 | <p>By submitting a validated CTS report, you receive public recognition of |
| 53 | your device's compatibility. This also opens up additional options you can |
| 54 | pursue such as use of the Android branding, access to Android Market, and |
| 55 | more.</p> |
| 56 | <p>As a consequence of some legal quirks, we aren't able to offer automatic |
| 57 | licensing of either the Android Market or branding. To actually obtain access |
| 58 | to these programs, you will need to <a |
| 59 | href="{@docRoot}compatibility/contact-us.html">contact us</a> to obtain a |
| 60 | license.</p> |