Are you viewing the right article?

This article refers to Digital Publishing Suite. For the AEM Mobile article, see Building apps for Android.

Use the Web-based DPS App Builder to create DPS apps for Android devices.

Previous versions of DPS allowed you to create legacy (AIR-based) Android apps. Creating or editing legacy Android apps is no longer supported.

Supported features in the native Android viewer

The native Android viewer supports most DPS features supported in iOS. Key Android viewer features include:

  • Android phones and tablets (5.1.1 or higher)
  • Pinch and zoom in articles with PDF, PNG, or JPEG image format
  • Scaling folios to fit the screen (any article format)
  • Google Play single-issue purchase

For a feature comparison chart, see DPS supported features list.

Files required to build native Android viewer

  • App icon in PNG format. We recommend a 96x96 PNG file.
  • Valid certificate. The certificate can be either a .p12 certificate or a .keystore file. For information about creating a valid .p12 certificate, see DPS Publishing Process for Android Devices.

Building a native Android viewer app

Use the Web-based DPS App Builder to build a native Android DPS app.

The Web-based DPS App Builder cannot sign the .apk file. Instead, use the DPS App Signing Tool to sign the app that can be submitted to the store, as described later in this document.

  1. Using an Adobe ID with a DPS App Builder role, sign in to the Web-based DPS App Builder:

    DPS App Builder
  2. Click the plus icon to build a new app.

  3. Choose Android from the Platform menu, and click Next.

  4. Follow the prompts to build the app.

General settings

In the General pane, specify these settings.

Application Name. Specify the name of the app. This name appears under the app icon and in the store UI.

Bundle ID. Specify a Bundle ID using the reverse DNS format, such as com.publisher.publication. Avoid using dashes or other special characters.

If you are updating an existing Android app, use the same Bundle ID specified previously in DPS App Builder.

Privacy Policy URL. (Optional) Specify the URL of a web page that describes your privacy policy.

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 Setting version numbers in Web DPS App Builder.

Application Account / Password. Select the Application account (also referred to as a "Title ID") used to publish the folios that will appear in the app library.

Apps Details
App Details (Enterprise account)


App Icon. Specify a PNG image file. If you specify a PNG size smaller or larger than 96x96, the content is scaled up or down as required.

Library Banner. If you sign in using an Enterprise account, the Library Banner option is available. You can upload a .zip file containing the HTML files used for the library banner. The source HTML file should be named "index.html." The banner adjusts its height to the full width of the device. You can use CSS media classes in your HTML to specify different images to appear on different device sizes.

If you no longer want the banner to appear after users sign in, select the "Hide banner when the reader is signed in" option. This option is especially useful for promotional subscription banners.



Library. If you sign in using an Enterprise account, you can specify the .zip file containing the HTML used for the custom library. The source HTML file should be named "index.html." For more information, see Creating a custom library (Enterprise).

Lock the Library to Landscape. Select this option if you want the library to be displayed in landscape orientation, even if the user rotates the device.

Configure Advanced Rendition Support. Select this option if you want to limit which folio sizes are available on Android phones and which folio sizes are available on Android tablets. The folio sizes that appear in the drop-down list include all the folios published as Public in the Application account you specified. Google considers devices that are 600 dpi or smaller to be phones.

Only the folio sizes you select are available on that device type. If you don't select a folio size for either device type, folios of that size will not appear in your Android app on that device type. If you select multiple folio sizes for a device type and set up renditions, the viewer will pick only the rendition that most closely matches the device dimensions.

For details, see Setting up renditions for native Android viewers.


Direct Entitlement (Enterprise only)

Select Enable Direct Entitlement only if your app uses direct entitlement (Enterprise only). Otherwise, click Next.

Integrator ID. Adobe provides the Integrator ID when your entitlement account is provisioned within our servers. This option is available only to DPS Enterprise customers. Contact your Adobe representative for information about the Integrator ID.

Create Account URL. Specify the URL where customers can sign up for a subscription through the publisher. This URL is used when users tap a “Create Account” button in the Sign In dialog box.

Forgot Account URL. Specify the URL where customers can retrieve their forgotten password.

Direct Entitlement

In-App Purchase

For information about setting up in-app billing for Android devices, see DPS Publishing Process for Android Devices.

In-App Purchase

Deleting and editing apps

To remove an app, select it and click the Trash icon.

To edit an instance of an app, select it and click the Edit App icon and follow the prompts. The app is rebuilt using the most current viewer version.

Updating and replacing an existing AIR-based Android app

If you're creating a new version for an existing AIR-based Android app, note the following:

  • Previous app settings and downloads are not preserved.
  • Folios downloaded in the AIR-based viewer are not removed when the app is updated. These files remain on the user's device.

Using the DPS App Signing Tool to sign the .apk file

When finished, download the .apk file for each store to which you would like to submit the app. Before submitting the app, use the utility to sign the .apk file.

To sign the app, you need either a .p12 certificate file or a .keystore file.

  1. In the Web-based DPS App Builder, click the Unsigned App link under "Downloads" to download the .apk file to your machine.

    This .apk file is unsigned. Before you submit it to the store, you must sign the .apk file.

  2. Download and install the DPS App Signing tool. This tool is available for download in the main page of Web DPS App Builder. Click the person icon in the upper right corner and choose Download Signing Tool from the menu.

    Download Signing Tool
  3. Launch the DPS App Signing Tool, and follow the prompts to sign the app.

    DPS App Signing Tool

    If you specify a .p12 certificate, specify the password. (For information on creating a .p12 certificate, see DPS Publishing Process for Android Devices.)

    If you specify a .keystore file, specify the keystore password, the private key alias, and the private key password.

  4. Submit the .apk file to the appropriate store. For details, see DPS Publishing Process for Android Devices.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy