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 |
Dan Morrill | a9788cd | 2009-11-15 11:49:30 -0800 | [diff] [blame] | 5 | devices. The purpose of the Android compatibility program is to help Android |
Dan Morrill | 98620ee | 2010-04-13 14:48:25 -0700 | [diff] [blame^] | 6 | device implementations remain compatible with apps.</p> |
Dan Morrill | a9788cd | 2009-11-15 11:49:30 -0800 | [diff] [blame] | 7 | <p>A device is considered compatible if existing and new third-party |
| 8 | applications run correctly on it. Poor device implementations that change APIs |
| 9 | or alter behaviors will break these apps and so are not compatible. The |
Dan Morrill | 98620ee | 2010-04-13 14:48:25 -0700 | [diff] [blame^] | 10 | Android Compatibility Program provides information and tools that device |
| 11 | implementers use to ensure that their devices are Android-compatible.</p> |
Dan Morrill | a9788cd | 2009-11-15 11:49:30 -0800 | [diff] [blame] | 12 | <p>The latest version of the Android source code and compatibility program is |
Dan Morrill | 98620ee | 2010-04-13 14:48:25 -0700 | [diff] [blame^] | 13 | 2.1, which roughly corresponded to the Eclair branch.</p> |
| 14 | |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 15 | <h2>Why build compatible Android devices?</h2> |
| 16 | <h3>Users want a customizable device.</h3> |
| 17 | <p>A mobile phone is a highly personal, always-on, always-present gateway to |
| 18 | the Internet. We haven't met a user yet who didn't want to customize it by |
| 19 | extending its functionality. That's why Android was designed as a robust |
| 20 | platform for running after-market applications.</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>Developers outnumber us all.</h3> |
Dan Morrill | 98620ee | 2010-04-13 14:48:25 -0700 | [diff] [blame^] | 23 | <p>No device manufacturer can hope to write all the software that a person could |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 24 | conceivably need. We need third-party developers to write the apps users want, |
| 25 | so the Android Open Source Project aims to make it as easy and open as |
| 26 | possible for developers to build apps.</p> |
Gaurav Mathur | 800158f | 2009-10-08 23:50:24 -0700 | [diff] [blame] | 27 | |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 28 | <h3>Everyone needs a common ecosystem.</h3> |
| 29 | <p>Every line of code developers write to work around a particular phone's bug |
| 30 | is a line of code that didn't add a new feature. The more compatible phones |
| 31 | there are, the more apps there will be. By building a fully compatible Android |
| 32 | device, you benefit from the huge pool of apps written for Android, while |
| 33 | increasing the incentive for developers to build more of those apps.</p> |
Gaurav Mathur | 800158f | 2009-10-08 23:50:24 -0700 | [diff] [blame] | 34 | |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 35 | |
| 36 | <h2>Android compatibility is free, and it's easy.</h2> |
| 37 | <p>If you are building a mobile device, you can follow these steps to make |
| 38 | sure your device is compatible with Android. For more details about the |
| 39 | Android compatibility program in general, see <a |
| 40 | href="{@docRoot}compatibility/overview.html">the program overview</a>.</p> |
| 41 | <p>Building a compatible device is a four-step process:</p> |
| 42 | <ol> |
Dan Morrill | 98620ee | 2010-04-13 14:48:25 -0700 | [diff] [blame^] | 43 | <li><b>Obtain the Android software source code</b><p>This is the |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 44 | <a href="{@docRoot}source/index.html">source code for the Android |
| 45 | platform</a>, that you port to your hardware.</p></li> |
Dan Morrill | 98620ee | 2010-04-13 14:48:25 -0700 | [diff] [blame^] | 46 | <li><b>Comply with Android Compatibility Definition Document (CDD)</b><p> |
| 47 | The CDD enumerates the software and hardware requirements of |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 48 | a compatible Android device.</p></li> |
| 49 | <li><b>Pass the Compatibility Test Suite (CTS)</b><p>You can use the CTS |
Dan Morrill | a9788cd | 2009-11-15 11:49:30 -0800 | [diff] [blame] | 50 | (included in the Android source code) as an ongoing aid to compatibility |
| 51 | during the development process.</p></li> |
Dan Morrill | 3cd199f | 2009-11-06 14:04:16 -0800 | [diff] [blame] | 52 | </ol> |
| 53 | |
Dan Morrill | 98620ee | 2010-04-13 14:48:25 -0700 | [diff] [blame^] | 54 | <h2>Joining the Ecosystem</h2> |
| 55 | <p>Once you've built a compatible device, you may wish to include Android |
| 56 | Market to provide your users access to the third-party app ecosystem. |
| 57 | Unfortunately, for a variety of legal and business reasons, we aren't able to |
| 58 | automatically license Android Market to any compatible device. To inquire |
| 59 | about access about Android Market, you can <a |
| 60 | href="{@docRoot}compatibility/contact-us.html">contact us</a></p> |