Follow the steps below to create the required certificate file and to learn how set up your Android app, test it, and submit it to Google Play. You can create an .apk app that you can submit to the Google Play Store.
For information about building the Android app, see Build Android apps (AEM Mobile).
Android systems require that all installed applications are digitally signed with a p12 certificate in which the private key is held by the application’s developer. Make sure that all applications are signed. The system can't install an application that is not signed. You can use self-signed certificates to sign your applications. No certificate authority is needed.
It's necessary that the certificate you create expires after October 22 2033.
Several methods for creating certificates are available, including Adobe Flash Professional and Adobe Flash Builder. If you don’t have any developer tools installed, you can use the Keytool utility to create a certificate. Keytool is a Java SDK utility that is already available on Mac OS computers. In Windows, it's necessary to install and configure Java SDK (also called JDK).
The following instructions tell you how to use Keytool to create a certificate. For detailed information, see Signing Your Application on the Android Developers site.
A certificate is created in your prompt location, such as your user name folder. Copy this certificate file to a known location, and save a backup copy. Write down the password as well.
Note: If a certificate file is not created, replace “-keystore myname.keystore” with a target path (such as -keystore c:\users\bob\bobcert.keystore) that you have access to.
You can use Google's In-app product service (also called "in-app billing") to sell collections within your app. Google Play subscriptions are not supported at this time.
Make sure that you set up your billing before you make your content available to customers.
For information on Google Play app pricing, see Selling Your Apps in Google Play Help.
Use the Google Play developer site to create an app request and to upload your custom viewer (.apk) app.
Follow the steps in the Administering In-app Billing Help topic. As you go through these steps, note the following:
- Specify the exact same In-app Product ID when setting up Android in-app billing that you use for the collection's Product ID. The Product ID ties the collection to the in-app billing item.
- For Purchase Type, select "Managed," not "Unmanaged." Otherwise, your customers can't restore purchases.
- Adobe does not support the Android Refund feature at this time.
- Note the "License Key" information. Adobe needs this information (also referred to as "shared secret") to enable in-app billing, as described in the next step.
In the Google Play Developer site, navigate to the "Services & APIs" section of the app. Copy the long string of characters under "Your License Key for This Application." In the On-Demand Portal, navigate to the Store section of project settings, and paste the license key value into the "Google Play Shared Secret" field.
1. Use the signing tool to sign the .apk file. See Signing iOS and Android apps for AEM Mobile.
2. Sign in to the Google Play Developer Portal and submit the signed .apk file to Google Play Store.
If your app includes retail in-app purchases, make sure that you specify the shared secret (license key) in the Store tab of project settings.
Make sure that you submit a beta APK file in the Google Play Developer Portal.