| Megha Joshi | 42d3a4a | 2010-08-17 13:56:59 -0700 | [diff] [blame] | 1 | <p>This sample demonstrates how to design an application that is compatible across different Android versions. Applications |
| 2 | should degrade gracefully on older platform versions, dropping features or providing |
| 3 | when the platform support needed by features or functionality isn't available.</p> |
| 4 | |
| 5 | <p>In this case, the CrossCompatibility application shows how to use APIs that are not available in all Android versions and |
| 6 | still create a single <code>.apk</code> that runs on all Android versions.</p> |
| 7 | |
| 8 | <ul> |
| 9 | <li>The main application's <a |
| 10 | href="AndroidManifest.html">AndroidManifest.xml</a> file declares that it is backwards compatible with API level 3 devices with attribute <code>minSdkVersion</code> in the <code>uses-sdk</code> tag. |
| 11 | </li> |
| 12 | <li> |
| 13 | <a |
| 14 | href="src/com/example/android/touchexample/VersionedGestureDetector.html">VersionedGestureDetector.java</a> |
| 15 | is a version independent abstract class which factors out multitouch APIs that differ between platform versions. </li> |
| 16 | |
| 17 | </ul> |
| 18 | |
| 19 | <p> For more information on how to make your applications cross-compatible, please check out the original |
| 20 | blogpost <a href="http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html">here</a>.</p> |