diff options
Diffstat (limited to 'docs/html/training/multiple-apks/api.jd')
| -rw-r--r-- | docs/html/training/multiple-apks/api.jd | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/html/training/multiple-apks/api.jd b/docs/html/training/multiple-apks/api.jd index 1a2593a..f43dcae 100644 --- a/docs/html/training/multiple-apks/api.jd +++ b/docs/html/training/multiple-apks/api.jd @@ -33,7 +33,7 @@ next.link=screensize.html <!-- other docs (NOT javadocs) --> <h2>You should also read</h2> <ul> - <li><a href="http://developer.android.com/guide/google/play/publishing/multiple-apks.html">Multiple APK + <li><a href="http://developer.android.com/google/play/publishing/multiple-apks.html">Multiple APK Support</a></li> <li><a href="http://android-developers.blogspot.com/2010/07/how-to-have-your-cupcake-and-eat-it-too.html"> @@ -57,7 +57,7 @@ necessary to make maintaining a multiple APK codebase as painless as possible.</ platform, naturally you want your application to take advantage of new features on new devices, without sacrificing backwards compatibility. It may seem at the outset as though multiple APK support is the best solution, but this often isn’t the case. The <a -href="{@docRoot}guide/google/play/publishing/multiple-apks.html#ApiLevelOptions">Using Single APK +href="{@docRoot}google/play/publishing/multiple-apks.html#ApiLevelOptions">Using Single APK Instead</a> section of the multiple APK developer guide includes some useful information on how to accomplish this with a single APK, including use of our support library. You can also learn how to write code that runs only at certain API levels in a single APK, without resorting to @@ -279,7 +279,7 @@ green ≥ blue. Therefore we can effectively collapse the chart to look lik <p> Now, let’s further assume that the Red APK has some requirement on it that the other two don’t. -<a href="{@docRoot}guide/google/play/filters.html">Filters on Google Play</a> page of +<a href="{@docRoot}google/play/filters.html">Filters on Google Play</a> page of the Android Developer guide has a whole list of possible culprits. For the sake of example, let’s assume that red requires a front-facing camera. In fact, the entire point of the red APK is to combine the front-facing camera with sweet new functionality that was added in API @@ -296,7 +296,7 @@ APK that supported that particular API level.</p> <p> In order to keep all your APKs on separate "tracks", it’s important to have a good version code scheme. The recommended one can be found on the <a -href="{@docRoot}guide/google/play/publishing/multiple-apks.html#VersionCodes">Version Codes</a> area of +href="{@docRoot}google/play/publishing/multiple-apks.html#VersionCodes">Version Codes</a> area of our developer guide. Since the example set of APKs is only dealing with one of 3 possible dimensions, it would be sufficient to separate each APK by 1000, set the first couple digits to the minSdkVersion for that particular APK, and increment from there. This might look like:</p> |