Requirements for building an Android app

You can use either Windows or Mac OS computers to build Android apps. Creating an Android app requires the "Manage Apps" permission.

The following items are required to build and sign an Android app:

  • Valid p12 certificate
  • 192x192-pixel app icon

For information about creating certificates, loading the test app, and submitting the app to Google Play Store, see Android publishing guide for AEM Mobile.

Building an Android app

  1. Make sure that your project settings include the appropriate information.

    Your project settings include several options that determine app features and behavior. For example, you can enable social sharing, article preview, and direct entitlement in project settings.

    It is not necessary to make these project settings before you create the app. When you edit project settings, those changes are automatically reflected in your app.

    For details, see Creating projects for AEM Mobile.

  2. In the On-Demand Portal (https://aemmobile.adobe.com), click Apps on the left rail. If you have access to more than one project, choose the project from the drop-down menu.

  3. Click the Add icon to create an app.

  4. Choose Android as the platform, and click Next.

  5. Follow the prompts to build the app. For detailed option descriptions, see the related section later in this article.

  6. Click Submit to build an unsigned app.

    For information about signing the app, see Signing iOS and Android apps for AEM Mobile.

App Details

App Name. The app name you specify appears below your app icon.

Bundle ID. The Bundle ID is the ID you specify when you submit the app in the Google Play Developer Console. The Bundle ID must include a period ( . ). Use all lowercase letters, and use the reverse DNS format such as com.company.application. For example, com.adobe.inspire is the Bundle ID for Adobe Inspire.

Privacy Policy URL. If you specify a privacy policy URL, a "Privacy Policy" option appears in the app settings menu. If a user taps Privacy Policy, the web page is displayed in an in-app browser.

Override the App Version Number. This option is necessary if you are updating an app and you used DPS App Builder or a different tool to create an existing app. Select this option and specify a more recent version number. For information on obtaining the app version number, see Changing the AEM Mobile app version number.

Enable Google Play In-App Purchase. Select this option if you want to sell collections. Use the Google Play Developer Console to set up in-app purchases that match the retail Product IDs used for your collections. For more information about setting up in-app billing, see Android Publishing Guide for AEM Mobile.

Show Analytics Opt-in Dialog Box. If you select this option, your customers can opt out of data tracking. They can use app settings to opt in or out at any time. This option is especially useful for regions in which you are obligated to allow users to opt out of data tracking.

Supported Devices. Choose "Phones and Tablets" to support all Android device types, or choose "Phones" or "Tablets" to limit the supported devices to phones or tablets.

According to Android guidelines, a phone is a device with a small or normal size. A tablet is a devices with a large or extra large screen size and a minimum width of 600 dp.

Tablet App Orientation/Phone App Orientation Specify the orientation for the tablet version of the app and the phone version of the app. Choose Landscape, Portrait, or Both.

If you choose the “Both” option, browse pages, HTML articles, and smooth scrolling PDF articles fill the screen in either orientation. InDesign-based or PDF-based fixed-layout articles are letterboxed to fit the screen when users rotate the device away from the article’s target orientation.

Enable Preflight. If this option is selected, the testing app you create displays all valid content, published or unpublished. Use this option only for previewing unpublished content, not for submitting to the Google Play Store. For details, see Previewing project content for AEM Mobile.

Enable Push Notifications. Select this option if you are using the Adobe Marketing Cloud to send push messages to Android app users. See Sending push messages using Marketing Cloud.

Assets settings

App Icon. Specify a 192x192 (recommended) PNG file. See Building AEM Mobile app icons and launch images.

Plug-ins settings

For information about Cordova plug-ins such as File Access and Geolocation, see Using Cordova plug-ins in AEM Mobile.

When to rebuild and resubmit apps

 

In general, you should rebuild your app for these reasons:

  • To edit an app setting, such as changing the app icon.
  • To take advantage of new viewer features or bug fixes in the latest release.
  • To use newly uploaded fonts or changes to app customization features. See Customizing AEM Mobile apps.
  • To include any changes made in the Mobile Marketing apps settings.

When you change nearly all project settings, you do not need to update your app. For example, you can specify store settings, set up entitlement, add subscription and product IDs, and enable social sharing without having to update the app. One exception to this rule is uploading fonts for cards. Fonts are built into the app, so you need to rebuild the app to use new fonts.

To rebuild an app, do this:

  1. Select the app in the Apps section of the On-Demand Portal and click the edit (pencil) icon.
  2. Make any changes, and click Submit.
  3. Download and sign the app.

Doing this rebuilds the app with the newest viewer code.

Эта работа лицензируется в соответствии с лицензией Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported  На посты, размещаемые в Twitter™ и Facebook, условия Creative Commons не распространяются.

Правовые уведомления   |   Политика конфиденциальности в сети Интернет