Home | History | Annotate | Download | only in practices

Lines Matching full:your

13     <li>If necessary, you can control distribution of your application based on the device
35 <p>Although we recommend that you design your application to function properly on multiple
36 configurations of screen size and density, you can instead choose to limit the distribution of your
39 Google Play by adding elements to your manifest file that specify the screen configurations your
42 <p>However, before you decide to restrict your application to certain screen configurations, you
45 them to the best of your ability. By supporting multiple screens, your application can be made
53 need to filter your application from larger screens. As long as you follow the <a
55 Independence</a>, your application should work well on larger screens such as tablets. However, you
56 might discover that your application can't scale up well or perhaps you've decided to publish two
57 versions of your application for different screen configurations. In such a case, you can use the <a
59 <compatible-screens>}</a> element to manage the distribution of your application based on
61 information to apply filtering to your application, so that only devices that have a screen
62 configuration with which you declare compatibility can download your application.</p>
66 {@code <screen>} element specifies a screen configuration with which your application is
72 <p>For example, if your application is compatible with only small and normal size screens,
76 configuration with which your application is <em>not</em> compatible. Here's what the manifest
77 entry looks like if your application is compatible with only small and normal screen sizes:</p>
102 <compatible-screens>}</a> element for the reverse scenario (when your application is not
106 to specify each screen density your application supports.</p>
113 <p>If you don't want your app to be used on handsets (perhaps your app truly makes sense only on a
115 devices from downloading your app by using the <a
119 <p>For example, if you want your application to be available only to tablet devices, you can declare
120 the element in your manifest like this:</p>
136 <p>This describes your app's screen-size support in two different ways:</p>
153 <p>Your size choice might be different, of course, based on how well your design works on different
154 screen sizes; for example, if your design works well only on screens that are 9" or larger, you
157 <p>The catch is that you must compile your application against Android 3.2 or higher in order to use
159 and will raise a compile-time error. The safest thing to do is develop your app against the platform
162 >. When you're making final preparations to build your release candidate, change the build target to
173 <supports-screens>}</a> element for the reverse scenario (when your application is not compatible
175 external services such as Google Play <strong>do not</strong> apply filtering. Your application
180 to prevent your application from being downloaded on larger screens, use <a
185 <p>Remember, you should strive to make your application available to as many devices as possible by
192 or you have decided to provide different versions of your application for different sets of screen
199 <p>Although we recommend that you publish one APK for your application, Google Play allows
203 version of your application, but you're unable to make the same APK work for both screen sizes,