# Android Publishing

### Before you publish your first app <a href="#before-you-publish-your-first-app" id="before-you-publish-your-first-app"></a>

#### Required Assets <a href="#required-assets" id="required-assets"></a>

We recommend you compile the following assets before embarking on the publishing journey.

* **App Information**
  * \[Text] App Name To be shown in the Play Store.
  * \[Text] A Short Description of your app
  * \[Text] A Full Description of your app
* **App Icon**
  * \[Image] 512 x 512 pixels
  * Up to 1MB in size
* **Feature Graphic**
  * \[Image] 1024 x 500 pixels
  * Up to 1MB in size
* **Phone Screenshots**
  * \[Images] 16:9 or 9:16 aspect ratio
  * Each side between 320 and 3,840 pixels
  * Up to 8MB in size

### App Settings <a href="#app-settings" id="app-settings"></a>

To publish your app on Android, you'll need the following items, to be added once you're preparing to publish:

* App Name
* Icon
* Application ID

### Each time you create a new app <a href="#each-time-you-create-a-new-app" id="each-time-you-create-a-new-app"></a>

**Create a new app on the Google Play Console**

1. Sign-in to your [**Google Play Console**](https://play.google.com/console/) account.
2. Click **Create app** in the upper right.
3. Complete the requested **app details** fields. Note: The App Name is how your app will appear on Google Play.
4. Complete the required **declarations**.
5. Click **Create app**.

#### Upload your Android App Bundle (AAB) file to the Google Play Console <a href="#download-your-android-app-bundle-aab-file" id="download-your-android-app-bundle-aab-file"></a>

The Apple and Android publishing processes are quite different. To publish with Apple, you complete the process in the Thunkable publishing wizard and the app file is sent directly to your Apple TestFlight. To publish with Android, you receive an email from Thunkable with your app's AAB file, which you download and then upload to the Google Play Store (Note, an AAB file cannot be installed on an Android device).

#### Manual method:&#x20;

To download your Android App Bundle (AAB) file:

1. Within your Thunkable project, click the **Publish** icon in the top right corner of your display.
2. Select **Publish Android** from the drop-down menu.

<figure><img src="/files/Y8w2Pg3LtsV4h0TOLqD5" alt=""><figcaption></figcaption></figure>

3. A publishing modal is provided to guide you through the publication process.
4. Enter the **email address** you want the app download link sent to.
5. Set your Application ID, App Icon, Version Name, and Version Code.
6. Click **Send**.

   <figure><img src="/files/mcet0g0xVf1vrWlLqx5r" alt=""><figcaption></figcaption></figure>
7. In approximately 30 minutes, you will receive your AAB file to the email address you provided.
8. When you receive the email, download the AAB file to your computer. Note: If you use Google Chrome, your browser settings may prevent you from downloading your AAB file. Simply open the email in Firefox or Safari to download your AAB file.

#### Automated method:&#x20;

To upload your Android App Bundle (AAB) file directly to the Google Play:

1. Setup Google Play API following the steps here: <https://ai.thunkable.com/account/playstore>
2. Within your Thunkable project, click the **Publish** icon in the top right corner of your display.
3. Select **Publish Android** from the drop-down menu.

<figure><img src="/files/Y8w2Pg3LtsV4h0TOLqD5" alt=""><figcaption></figcaption></figure>

4. A publishing modal is provided to guide you through the publication process:

<figure><img src="/files/LBKT5EY14eBNOn5q771b" alt=""><figcaption></figcaption></figure>

5. Enter the **email address** you want the app download link sent to.
6. Set your Application ID, App Icon, Version Name, and Version Code.
7. Click on the checkbox "Publish to Google Play after build":

<figure><img src="/files/qJryIdxJ7om5OAqNo2zF" alt=""><figcaption></figcaption></figure>

8. Click **Send**.
9. In approximately 30 minutes, your AAB file will be sent to the Google Play platform.

#### Manage your app signing <a href="#manage-your-app-signing" id="manage-your-app-signing"></a>

![](https://docs.thunkable.com/~gitbook/image?url=https%3A%2F%2F1223006790-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-legacy-files%2Fo%2Fassets%252F-LAn5scXl2uqUJUOqkJo%252F-MbKl54vHyH1-Kw3fqBM%252F-MbKvhB85b_I-diO0Ku-%252FPrepare-1.png%3Falt%3Dmedia%26token%3Da6647069-a2fc-4a7e-a04d-893d660075fb\&width=768\&dpr=4\&quality=100\&sign=51dff9d9\&sv=2)

Google will offer to protect your app signing key. You can click **Continue** to allow this to proceed. You will only be asked this the first time you publish a release.

If you don't want Google to manage your App Signing, you can do so yourself. This is not necessary.

Continue following the instructions in this document from Create and Publish a Release.

**App Dashboard**

While you're getting set up, the Google Play Console Dashboard shows you what you need to do to get your app up and running. This includes recommendations on how to manage, test, and promote your app. Once you've completed a task, return to the Google Play Console Dashboard to explore what else you need can do.

We'll focus on the following steps:

* Set up your app
* Publish your app on Google Play

**Set up your app**

In this section, you'll share with Google the content of your app, and manage how it is organized and presented on Google Play.

1. Click **View tasks** in the Set up your app section to see the tasks you must complete.
2. Click on a task.
3. Complete the required fields.
4. Click **Save**.
5. Click **Dashboard** above the task name in the upper left.
6. Repeat with the remaining tasks in the list.

Apps that request access to sensitive permissions or data (as defined in the [user data policies](https://play.google.com/about/privacy-security-deception/user-data/)) are required by the Google Play Store to include a privacy policy. All apps made on Thunkable request access to sensitive permissions or data, which means you will need to provide a privacy policy.

**Main store listing**

1. Click **Main store listing** under the Grow heading in the sidebar.
2. Complete the required fields and upload the required assets. See here for additional guidance: [Add preview assets to showcase your app](https://support.google.com/googleplay/android-developer/answer/9866151).
3. Click **Save**.

**Create and publish a release**

1. Return to the Google Play Console **Dashboard**.
2. Click **View tasks** in the Create and publish a release section to see the tasks you must complete.
3. Click the **Select countries** task.
4. Identify the countries you want your app to be available in.
5. Click **Create a new release**.
6. Upload the AAB file into the **App bundles** section. Instructions for downloading your AAB are available here: Download your Android App Bundle (AAB) file
7. Add **Release notes** for this update.
8. Click **Next**.

You may see some Accessibility, Performance, Stability, Security, and trust warnings on the Google Play Store, Pre-launch report. These notifications from Google about your app are simply some warnings, not errors--there is nothing wrong with your app and it should still appear on the Play Store.

### To update your app <a href="#to-update-your-app" id="to-update-your-app"></a>

### **Updating an existing app on the Play Store** <a href="#updating-an-existing-app-on-the-play-store" id="updating-an-existing-app-on-the-play-store"></a>

1. In your Google Play Console, click on the **Releases** tab.
2. Click the **Create New Release** Button
3. Upload the AAB file into the **App bundles** section. Instructions for downloading your AAB are available here: Download your Android App Bundle (AAB) file.
4. Add a **Release name** so you can identify this release. It isn't shown to users on Google Play.
5. Add **Release notes**. Let users know what's in your release.
6. Click **Next**.

If you are updating an existing app on the Google Play Store, your Thunkable project will need to have:

* The same package name as the published app
* An incremented version number (version number is higher than the version number of your published app). This can be updated in your project's code.

You will not need to change any app signing settings when updating a published app.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://aidocs.thunkable.com/publishing/android-publishing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
