diff options
Diffstat (limited to 'docs/html/guide/practices/screens-distribution.jd')
| -rw-r--r-- | docs/html/guide/practices/screens-distribution.jd | 30 |
1 files changed, 26 insertions, 4 deletions
diff --git a/docs/html/guide/practices/screens-distribution.jd b/docs/html/guide/practices/screens-distribution.jd index 0c5193b..951e364 100644 --- a/docs/html/guide/practices/screens-distribution.jd +++ b/docs/html/guide/practices/screens-distribution.jd @@ -17,6 +17,7 @@ screen configuration</li> <ol> <li><a href="#FilteringHansetApps">Filtering a Handset Application from Tablets</a></li> <li><a href="#FilteringTabletApps">Filtering a Tablet Application from Handsets</a></li> + <li><a href="#MultiApks">Publishing Multiple APKs for Different Screens</a></li> </ol> <h2>See also</h2> @@ -43,7 +44,7 @@ application supports.</p> should understand the techniques for <a href="{@docRoot}guide/practices/screens_support.html">supporting multiple screens</a> and implement them to the best of your ability. By supporting multiple screens, your application can be made -available to the greatest number of users with different devices, using a single {@code .apk}.</p> +available to the greatest number of users with different devices, using a single APK.</p> @@ -144,9 +145,9 @@ href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code with <em>larger</em> screens) and set the larger screen size attributes to {@code "false"}, then external services such as Android Market <strong>do not</strong> apply filtering. Your application will still be available to larger screens, but when it runs, it will not resize to fit the screen. -Instead, the system will draw it in a "postage stamp" window that's the same relative size as the -screen size that your application does support (see <a -href="screens-support-1.5.html#CompatMode">compatibility mode</a> for more information). If you want +Instead, the system will emulate a handset screen size (about 320dp x 480dp; see <a +href="{@docRoot}guide/practices/screen-compat-mode.html">Screen Compatibility Mode</a> for more +information). If you want to prevent your application from being downloaded on larger screens, use <a href="{@docRoot}guide/topics/manifest/compatible-screens-element.html">{@code <compatible-screens>}</a>, as discussed in the previous section about <a @@ -162,3 +163,24 @@ href="{@docRoot}guide/topics/manifest/supports-screens-element.html">{@code or you have decided to provide different versions of your application for different sets of screen configurations.</p> + + +<h2 id="MultiApks">Publishing Multiple APKs for Different Screens</h2> + +<p>Although we recommend that you publish one APK for your application, Android Market allows +you to publish multiple APKs for the same +application when each APK supports a different set of screen configurations (as declared in +the manifest file). For example, if you want to publish both a handset version and a tablet +version of your application, but you're unable to make the same APK work for both screen sizes, +you can actually publish two APKs for the same application listing. Depending on each device's +screen configuration, Android Market will deliver it the APK that you've declared to support that +device's screen.</p> + +<p>Beware, however, that publishing multiple APKs for the same application is +considered an advanced feature and <strong>most applications should publish only one +APK that can support a wide range of device configurations</strong>. Supporting multiple screen +sizes, especially, is within reason using a single APK, as long as you follow the guide to +<a href="{@docRoot}guide/practices/screens_support.html">Supporting Multiple Screens</a>.</p> + +<p>If you need more information about how to publish multiple APKs on Android Market, read <a +href="{@docRoot}guide/market/publishing/multiple-apks.html">Multiple APK Support</a>.</p> |