标签：
Google Play uses the filter restrictions described below to determine whether to show your application to a user who is browsing or searching for applications from the Google Play app.
When determining whether to display your app, Google Play checks the device‘s hardware and software requirement, as well as it‘s carrier, location, and other characteristics. It then compares those against the restrictions and dependencies expressed by the application‘s manifest file and publishing details.
If the application is compatible with the device according to the filter rules, Google Play displays the application to the user. Otherwise, Google Play hides your application from search results and category browsing, even if a user specifically requests the app by clicking a deep link that points directly to the app‘s ID within Google Play.
Most filters are triggered by elements within an application‘s manifest file, AndroidManifest.xml (although not everything in the manifest file can trigger filtering). Table 1 lists the manifest elements that you should use to trigger filtering, and explains how the filtering for each element works.
Table 1. Manifest elements that trigger filtering on Google Play.
| Manifest Element | Filter Name | How It Works |
<supports-screens> |
Screen Size |
An application indicates the screen sizes that it is capable of supporting by setting attributes of the As a general rule, Google Play assumes that the platform on the device can adapt smaller layouts to larger screens, but cannot adapt larger layouts to smaller screens. Thus, if an application declares support for "normal" screen size only, Google Play makes the application available to both normal- and large-screen devices, but filters the application so that it is not available to small-screen devices. If an application does not declare attributes for
Example 1 Example 2 Example 3 For more information on how to declare support for screen sizes in your
application, see |
<uses-configuration> |
Device
Configuration: keyboard, navigation, touch screen |
An application can request certain hardware features, and Google Play will show the app only on devices that have the required hardware. Example 1 Example 2 For more details, see |
<uses-feature> |
Device Features |
An application can require certain device features to be present on the device. This functionality was introduced in Android 2.0 (API Level 5). Example 1 Example 2 For complete information, see Filtering based on implied features: In some cases, Google
Play interprets permissions requested through
|
| OpenGL-ES
Version |
An application can require that the device support a specific
OpenGL-ES version using the Example 1 Example 2 Example 3 Example 4 For more details, see |
|
<uses-library> |
Software Libraries |
An application can require specific shared libraries to be present on the device. Example 1 Example 2 For more details, see |
<uses-permission> |
Strictly, Google Play does not filter based on
<uses-permission> elements. However, it does read the
elements to determine whether the application has hardware feature requirements
that may not have been properly declared in <uses-feature>
elements. For example, if an application requests the CAMERA
permission but does not declare a <uses-feature> element for
android.hardware.camera, Google Play considers that the
application requires a camera and should not be shown to users whose devices do
not offer a camera.
In general, if an application requests hardware-related permissions,
Google Play assumes that the application requires the underlying hardware
features, even though there might be no corresponding to
For a list of permissions that imply hardware features, see
the documentation for the |
|
<uses-sdk> |
Minimum Framework Version (minSdkVersion) |
An application can require a minimum API level. Example 1 Example 2 Because you want to avoid this second scenario, we recommend that you always declare a |
Maximum Framework Version (maxSdkVersion) |
Deprecated. Android
2.1 and later do not check or enforce the Declaring |
In addition to the manifest elements in table 1, Google Play can also filter applications based on the advanced manifest elements in table 2.
These manifest elements and the filtering they trigger are for exceptional use-cases only. These are designed for certain types of high-performance games and similar applications that require strict controls on application distribution. Most applications should never use these filters.
Table 2. Advanced manifest elements for Google Play filtering.
| Filter Name | How It Works |
|
|
Google Play filters the application if the device screen size and density does not match any of the screen configurations (declared by a Caution: Normally, you should not use this manifest element. Using this element can dramatically reduce the potential user base for your application, by excluding all combinations of screen size and density that you have not listed. You should instead use the |
<supports-gl-texture> |
Google Play filters the application unless one or more of the GL texture compression formats supported by the application are also supported by the device. |
Google Play uses other application characteristics to determine whether to show or hide an application for a particular user on a given device, as described in the table below.
Table 3. Application and publishing characteristics that affect filtering on Google Play.
| Filter Name | How It Works |
| Publishing Status |
Only published applications will appear in searches and browsing within Google Play. Even if an app is unpublished, it can be installed if users can see it in their Downloads area among their purchased, installed, or recently uninstalled apps. If an application has been suspended, users will not be able to reinstall or update it, even if it appears in their Downloads. |
| Priced Status | Not all users can see paid apps. To show paid apps, a device must have a SIM card and be running Android 1.1 or later, and it must be in a country (as determined by SIM carrier) in which paid apps are available. |
| Country Targeting | When you upload your app to Google Play, you can select the countries in which to distribute your app under Pricing and Distribution. The app will then be available to users in only the countries you select. |
| CPU Architecture (ABI) | An application that includes native libraries that target a specific CPU architecture (ARM EABI v7 or x86, for example) are visible only on devices that support that architecture. For details about the NDK and using native libraries, see What is the Android NDK? |
| Copy-Protected Applications | Google Play no longer supports the Copy Protection feature in the Developer Console and no longer filters apps based on it. To secure your app, please use Application Licensing instead. See Replacement for Copy Protection for more information. |
Filtering in Google Play is based on several types of app metadata and configuration settings, including manifest declarations, required libraries,architecture dependencies, and distribution controls set in the Google Play Developer Console, such as geographic targeting, pricing, and more.
Google Play filtering is based in part on manifest declarations and other aspects of the Android framework, but actual filtering behaviors are distinct from the framework and are not bound to specific API levels.
How Filters Work on Google Play
标签：
原文地址：http://www.cnblogs.com/solo-heart/p/4806424.html
