Tag Archives: filtering

Checking your app. against Android Market technical filters

As android is designed to run on many different type of devices so an app has to be designed such that it is able to cope variety of devices with different hardware. I been working on an android app which uses internet so its not a must to have wifi for the device as it could just as well connect with 3G. I wanted to be sure that the app will be available for devices that might not have wifi but still could connect using 3G. This can be configured through the <uses-feature> tag in the application AndroidManifest.xml:

<uses-feature android:name="android.hardware.wifi" android:required="false" />

What android market does is that it filters the applications for a device so that users see and download only those applications which are compatible with their device. The market filtering is based on explicit and implicit features of an application and it is implemented in part by the aapt tool. A developer can check against this filtering by the following command:

$ aapt dump badging <path_to_exported_.apk>

The tool will return you a lot of other information such as what screen size and density an application is compatible with, what language it supports etc. The aapt tool can be found under SDK Install Dir/platforms/android-x/tools or SDK Install Dir/platform-tools

Here is the output by the above command for my application:

package: name=’guestshots.activities’ versionCode=’1′ versionName=’1.0′
sdkVersion:’7′
uses-permission:’android.permission.INTERNET’
uses-permission:’android.permission.WAKE_LOCK’
uses-permission:’android.permission.ACCESS_NETWORK_STATE’
uses-permission:’android.permission.ACCESS_WIFI_STATE’
uses-feature-not-required:’android.hardware.wifi’
application: label=’GuestShots’ icon=’res/drawable-mdpi/logo.png’
launchable activity name=’guestshots.activities.AccountSetup’label=’GuestShots’ icon=”
uses-feature:’android.hardware.touchscreen’
main
other-activities
other-receivers
other-services
supports-screens: ‘small’ ‘normal’ ‘large’
supports-any-density: ‘true’
locales: ‘–_–‘
densities: ‘120’ ‘160’ ‘240’

So looking at this output I’m 100% sure that my app. doesn’t force the wifi requirement and will be available for all three density and screen size devices and that a device need to have touch screen in order to use my application.