One of the key features of Kotobee Author is the native mobile app export option. Generating a native mobile app generally is a complex process, especially when targeting different device platforms. Kotobee Author supports exporting to three different mobile platforms: Android, iOS, and Windows Phone.

The app creation process

Contrary to the other export formats, the creation process for native mobile apps happens on our servers rather than your machine. Therefore, you will not instantly receive the app, but you will need to wait a few minutes until the app has completed its generation workflow on our servers. When the app generation is complete, you will be sent an email notification with the download link for the app. You can always track the status of the app in the generation workflow by going to the Manage screen from the header bar, and clicking on Apps in the left menu. 

There are 4 different phases, represented by different statuses. Any status change will cause an email notification to be sent to you.


The app is in the queue and waiting for its turn to build. The duration of this phase depends on the congestion of the queue. Apps are served at first come first server basis.


The app has actually started building. This phase should take few minutes at most.


The app has finished building and available for download.


For some reason, the app has failed to compile. An error message will be provided.


The app has expired and no longer available. This may happen with completed apps that have been left for a long time.

App generation is controlled by your account credits. A credit is deducted per platform, only once the generation process is successful and you have received the app file. Go back to the Export screen and click on Export Native Mobile App. At the footer you will be able to see the number of credits you have, and the number of credits required for app creation.

Setting app information

All platforms (Android, iOS, Windows phone) that you decide to export to, share some required information. This information is entered in the App information box shown in the mobile app export screen.

App Name

The name representing your app on the app menu.

Package ID

A unique ID representing your app. A typical pattern to use is your reverse domain name.

App Version

The app version. This value is important for updating the same app in future.


A brief description of the app.

 Lock the app to a specific orientation, or allow it to adjust to all orientations (default).
 Splash Color
 A splash screen is shown for very few seconds before the app starts. You may choose the color of the screen. The default is purple.

App Icon

The app icon appearing in the app menu. A 512px by 512px PNG image is recommended.

 Permitted devices
 Make a list of the devices that are allowed access to your app. You can identify each device using the IMEI, UDID, or MAC address. This feature is not supported for iOS devices.
 Display ads
 Make money from your app using AdMob (from Google). An AdMob Publisher ID is required. To create an AdMob account, please refer to this link.
 Optimizing causes unused images and files to be deleted, producing smaller file size. Avoid optimizing if you have manually added images through the file manager, and will access them using Javascript

You may also use your app as a cloud ebook. This gives it extra privileges such as user access control, note synchronization, and much more. For more information on cloud ebooks, please read: Understanding cloud ebooks.

To select the platform(s) that you want to export to, you should enable them by clicking on the Enable button under each platform box. Each exporting platform requires some information that is specific to the platform only, as will be seen below.

Exporting an Android app

These are the options specific to Android app creation.

Create random keystore

Auto-generate a random keystore file, and fill in the fields with the appropriate alias and password.

Keystore file

All apps must be digitally signed with a certificate. With the latest versions of Kotobee Author, you can create a random keystore automatically through the Create random keystore button. If you'd prefer to use your own keystore, please refer to this link to create an Android keystore file:

Keystore alias

The alias used by the keystore.

Keystore password

The password used by the keystore, if one exists.

Private key password

The password used by your key, if one exists.

Android Version Code

Version code in Android’s format. The Android version code should be an integer (decimals strictly forbidden and will result in an error).

Exporting an iOS app

These are the options specific to iOS app creation.

p12 Certificate file

All apps must be digitally signed with a p12 certificate. For instructions to create this file, please refer to the following knowledge-base tutorial.

Provisioning profile

A .mobileprovision file is required for iOS app creation. You may create this using your Apple Developer account.

Certificate password

The password to access your certificate. This value is optional, unless a password exists.

CFBundle version

The build-version-number string for the bundle. This value is optional.

For help on submitting to the App Store, or for getting the p12 certificate or provisioning profile, please follow the tutorial: Exporting an iOS app to the App Store.

Exporting a Windows Phone app

For Windows Phone app creation, the only piece of information required is the Publisher ID. This can be obtained after signing for a developer account with Microsoft.