We’re here to help

Creating a single-issue app for Android

Follow

Use the build settings wizard to go through the process step by step

When creating an app build for the first time, a configuration wizard will walk you through the different steps and options of the build process. Once you saved that setting, you will be able to re-use it later for generating an update of that app.

Below is an overview of the different steps involved for creating a single-issue Android app.

1. Choose a name for your setting

Usually the build setting name will refer to the publication name.

1. Choose a name for your setting

2. Choose the Application Type

Here you can select the type of app you wish to build:

2. Choose the Application Type

Single Issue

This will generate a standalone app that contains the contents for a single issue of your publication. When creating an update of this app, all existing contents will be replaced by the new version. Android apps can then be submitted to Google Play.

3. General Settings

3. General Settings

3.1. General

Application name

This is the name users will see on the home screen of the device.

Build for

Choose whether you want an app that supports Tablets, Phones, or both.

3.2. UI Language

Here you can select the languages your app will support - alerts and error messages in your app will then be displayed in the system language specified on the device. 

3.3. App Store Rating

If you want to prompt the reader to rate your app on the app store, you need to check this option.

4. Analytics

4. Analytics

4.1. Google Analytics

  • If you want to gather analytics data for your publication, enter your web tracking code in the form of UA-XXXXX-Y.
  • You need to have a Google Analytics account to do this. In that account, create a mobile app entry for your publication.
  • Full analytics setup info is available here.

4.2. Localytics

Localytics can only be used with Multi-Issue Apps

4.3. Twixl Publisher Platform

Twixl Publisher Platform Analytics are not possible with Single-Issue Apps.

5. Artwork

5. Artwork

5.1. App Icon

The app icon that will be displayed in the Home Screen of the device. Should have a size of 1024x1024 pixels.

5.2. Startup Screens for Tablets

These screens will be displayed while the app is starting up (if you do not select any images, the default ones will be used). They need to have the following dimensions:

  • Android Portrait: 800 x 1232 pixels
  • Android Landscape: 1280 x 752 pixels

5.3. Startup Screens for Phones

These screens will be displayed while the app is starting up (if you do not select any images, the default ones will be used). They need to have the following dimensions:

  • Portrait (4:3): 640 x 960 pixels
  • Portrait (16:9): 1242 x 2208 pixels
  • Landscape (16:9): 2208 x 1242 px

6. Code Signing

6. Code Signing

Code signing is a security measure to provide proof that you are indeed the publisher of an app.

Android Code Signing

Android Application ID

This should be a reverse DNS name like com.yourdomain.yourpublication - if you are going to be creating an app for both the iPad and Android, the best practice is to use the same one as the one you used for the iPad.

Android Keystore

If you are moving to Twixl Publisher from a platform like Adobe DPS, you will have created an Android keystore using the Keytool via terminal. You can find more info about the Android Keystore in this article.

7. Create build

6. Create build

Your are now ready to create a build of your app, according to the settings you specified. Later on you can also check the "Advanced Settings" to adjust more advanced settings that are not included in the wizard. 

8. Application options

8. Application options

When you create a build, you will get different options for your build, as shown below:

Version

Allows you to increment the version when you are updating your app

Platforms

Android - select Test build to create a version for internal testing, Android for Google Play for submitting to the Play store.

Publication

Select the InDesign export file here (with the .publication extension)

9. Build process…

9. Build process…

The app will display information about the current build status.

10. Build succesful!

10. Build succesful!

When the build process has completed, you will be able to navigate to the resulting files in the Finder.

11. Resulting file(s)

11.1. For a test build

The resulting file will have an extension .apk

You are now ready to deploy your app.

11.2. For a Google Play build

There will be two files:

  • a file with extension .apk (the app itself)
  • a file with extension .obb (the publication)

You are now ready to deploy your app.

Was this article helpful?
0 out of 0 found this helpful