Preparing the Android Manifest File for Release

Before release, you need to make a number of changes to the application configuration settings of the Android manifest file. Some of these changes are simply common sense, and others are imposed by marketplaces such as the Android Market.

You should review the Android manifest file as follows:

□ Verify that the application icon (various sizes of PNG) is set appropriately. This icon will be seen by users and is often used by marketplaces to display the application.

□ Verify that the application label is set appropriately. This represents the application name as users will see it.

□ Verify that the application version name is set appropriately. The version name is a friendly version label that developers (and marketplaces) use.


□ Verify that the application version code is set appropriately. The version code is a number that the Android platform uses to manage application upgrades. Consider incrementing the version code for the release candidate in order to differentiate it from the prerelease version of the application.

□ Confirm that the application uses-sdk setting is set correctly. You can set the minimum, target, and maximum Android SDK versions supported with this build. These numbers are saved as the API level of each Android SDK. For example, Android 2.1 is API level 7.

Did you Know?

□ Disable the debuggable option.

□ Confirm that all application permissions are appropriate. Request only the permissions the application needs with uses-permission, and make sure to request permissions the application uses, regardless of handset behavior without them.

0 0

Post a comment