Developing Android Applications with Adobe AIR [16]
Here are the required tags:
// Last segment specifies the version of AIR required // Universally unique identifier. // Android converts ID to a package name by adding // "air." to the beginning. // Hyphens are converted to underscore // and digits are preceded by a capital A. // name used for the APK package file // contains three integers, up to three digits each // properties of initial appearance of the application // root swf // application takes over the whole screen if true // portrait (default) or landscape // true (default) or false // cpu (default) or gpu
The following tags are optional. They are child nodes of the application tag:
// or localized
// name as it appears on device. Keep it short
// Displayed in installation dialog // Update handled by user on double-click or automatic // can be launched from link in a browser // Add all permissions as children of manifest tag "android.intent.category.LAUNCHER"/> ]]> Setting Permissions Use the permission tag in the application descriptor to list all the permissions needed, as shown in the code below. Permissions cannot be modified at runtime. Just before installing an application, the Android Market displays the permissions required. Figure 4-1 shows that Queue Manager, an application for managing your Netflix queue, only requires the Internet permission. WARNING Before submitting your application, verify that you only include the permissions needed. Otherwise, you may filter out a group of users who will not see your application in their version of the Android Market. To make network requests. Can be used for remote debugging To write data to external storage, such as the SDCard Read-only access of phone state. Used to mute AIR in case of incoming call
The Android security and privacy model requires permissions to access certain features such as GPS. When clicking the Install button, the user sees the list of permissions and can then make an educated decision to opt out if desired.