> For the complete documentation index, see [llms.txt](https://aidocs.thunkable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aidocs.thunkable.com/publishing/store-listing.md).

# Store listing

The **Store Listing** page helps you prepare your app for publishing to the **App Store** and **Google Play**. It combines automated validation, AI-assisted content generation, and store-specific requirements into a single workflow so you can identify and resolve publishing issues before submitting your app.

Instead of discovering missing requirements after starting a publish, you can use the Store Listing checklist to see what is complete, what still needs attention, and where each remaining task should be completed.

You can switch between the **App Store** and **Google Play** tabs at any time to configure the requirements for each platform independently.

## Open the Store listing

To open your Store Listing:

1. Open your project.
2. Click **Publish**.
3. Select **Store Listing**.
4. Select either **App Store** or **Google Play**.

{% hint style="info" %}
You could also ask the AI to publish your app by sending a relevant prompt into the chat. For example: "Publish my app"
{% endhint %}

At the top of the Store Listing, Thunkable displays the number of requirements that still need to be completed.

The left-hand navigation organizes the information you need to provide into sections such as:

* **Checklist**
* **App icon & artwork**
* **Screenshots**
* **Store text**
* **Privacy policy**
* **Data safety** for Google Play
* **Preview**

Requirements with a **green checkmark** are complete, and requirements shown in **red** need to be resolved before publishing.&#x20;

Where possible, Thunkable provides an action next to an incomplete requirement and selecting an incomplete item or its action takes you to the relevant place to resolve it.

Some requirements can be handled directly by Thunkable, while others must be completed in **App Store Connect** or **Google Play Console**.

##

### App Store (iOS)

Select the **App Store** tab to prepare your iOS Store Listing.

#### Automated by Thunkable

Thunkable AI can check and help complete the following requirements whenever possible:

* Account Plan allows publishing.
* Active App.
* Bundle ID.
* App version.
* App Store Connect API credentials.
* iOS permission descriptions.
* Bundle ID in Apple Developer.
* App version on the App Store.
* App Secrets.
* AdMob requirements (if applicable).
* App icon.
* Privacy Policy URL.
* Store screenshots.
* Store title.
* Store description.
* App Store keywords.
* App Store category.
* Support URL.
* App Review contact information.
* Reviewer sign-in requirements.

#### Manual in App Store Connect

The following steps must be completed manually in **App Store Connect**:

* App exists in App Store Connect.
* App Privacy questionnaire.
* Age Rating.
* Pricing & Availability.
* Content Rights information.

### Google Play (Android)

Select the **Google Play** tab to prepare your Android Store Listing.

Google Play has some requirements that differ from the App Store, so completing your iOS listing does not necessarily mean your Google Play listing is ready.

#### Automated by Thunkable

Thunkable AI can check and help complete the following requirements whenever possible:

* Account Plan allows publishing.
* Active App.
* Package name.
* App version.
* Google Play service account.
* Automated Google Play publishing.
* App Secrets.
* AdMob requirements (if applicable).
* App icon.
* Privacy Policy URL.
* Feature graphic (1024 × 500).
* Store screenshots.
* Store title.
* Store description.
* Google Play short description.
* Support email.

#### Manual in Google Play Console

The following steps must be completed manually in **Google Play Console**:

* Data Safety form.
* Content Rating questionnaire (IARC).
* Play Store category.

{% hint style="info" %}
Selecting an incomplete item will guide you to the relevant section where it can be completed.
{% endhint %}

{% hint style="info" %}
AI-generated content consumes AI tokens.
{% endhint %}

## Store Listing Tab

### Checklist

#### Bundle ID

Your app's **Bundle ID** uniquely identifies your app.

Before your first upload, double-check that the Bundle ID is correct. Once the app has been uploaded to the stores, changing its identity is not part of the normal update flow.

#### App Review information

Apple may need additional information to review your app.

Provide the requested **App Review contact information** so Apple's review team can contact you if necessary.

If your app requires an account or sign-in to access important functionality, also provide the reviewer with the required sign-in information.

### App icon & artwork

**Generate with AI** (400 AI tokens per run) or **upload your own** app icon.&#x20;

Google Play requires a **1024 × 500 feature graphic** for the store listing. You can **generate it with AI** (400 AI tokens per run) or **upload your own** image.&#x20;

### Screenshots&#x20;

Screenshots allow users to preview your app before downloading it.

Thunkable can help capture the required screenshots. Open **Screenshots** to review or prepare the screenshots that will be included with your Store Listing.

### Store text

The **Store text** section contains the text customers see when they discover your app in the Stores.

Complete the required information, including:

* Store title
* Store description
* App Store keywords
* App Store category
* Support URL

You can use **AI to help create store listing content** (800 AI tokens per run to generate all text or 100 AI tokens per run for each text) or **add your own** text.&#x20;

### Privacy policy

A Privacy Policy URL is required as part of the publishing configuration.

You can either use a privacy policy hosted for you through the available Thunkable publishing workflow or provide the URL of a privacy policy that you host yourself.

If you use your own policy, enter its public URL and make sure the page is accessible without requiring users to sign in.

If you use the hosted privacy policy option, you can review and edit the policy content before using its generated URL in your Store Listing.

### Data Safety

Google Play requires developers to complete the **Data Safety** form.

Open the **Data safety** section of the Store Listing to review the information relevant to your app. The final declarations required by Google must accurately reflect how your app collects, shares, and handles user data.&#x20;

You can **use AI to** draft it (100 AI tokens per run) from what your app actually does, then complete the form once in the Play Console.

Because these declarations concern your app's actual data practices, review them carefully before submitting them in Google Play Console.

### Preview Your Store Listing

Use **Preview** to review your Store Listing before publishing.

Check the:

* App icon
* Screenshots
* Store title&#x20;
* Subtitle
* Description

### Publish App

Click **Publish App** to submit your app for publishing using the current Store Listing configuration.

Before publishing, Thunkable validates your app against the selected platform's publishing requirements. If any required items are missing, you'll be prompted to complete them before continuing.

Once all requirements are met, Thunkable builds your app and uploads it to the selected app store using your configured publishing settings.

{% hint style="info" %}
You can follow the publishing progress directly in the chat. Thunkable will provide real-time status updates, notify you when each publishing step is completed, and guide you through any remaining manual actions required before your app is successfully published.
{% endhint %}

## Follow Publishing Progress in Chat

After you trigger publishing, you can follow the process directly in the Thunkable chat.

The publishing assistant checks the selected store and displays the current status, including how many requirements are passing.

For example, when everything is ready, you may see:

**Ready to publish to the App Store**

along with all checks passing and a **Publish to the App Store** action.

<div align="left"><figure><img src="/files/UrXFt59hiouD4Qh2MJdF" alt="" width="563"><figcaption></figcaption></figure></div>

If requirements remain, the chat instead displays an **Almost ready** status and tells you how many items still need to be completed.

For example:

**Almost ready for Google Play**\
**2 items to finish before you can publish to Google Play**

The missing requirements are displayed directly in the chat with actions such as **Configure credentials**, allowing you to resolve them without having to determine the problem yourself.

<div align="left"><figure><img src="/files/emwp4rCFGaeryNMP4w0P" alt="" width="563"><figcaption></figcaption></figure></div>

### When Thunkable Cannot Complete the Submission Automatically

A successful build and upload does not always mean that the app has been submitted for review.

Apple or Google may require information that cannot be completed automatically.

For example, after an App Store upload, you may see a message such as:

**Apple wouldn't accept the automatic submission yet, a few items still need attention.**

Thunkable then explains what remains to be completed in App Store Connect.

Your binary may already be successfully uploaded even though submission for review has not yet occurred.

In this situation:

1. Read the message in the publishing chat to identify the missing requirement.
2. Select **Open the Store**.
3. Complete the requested information in the Store.
4. Submit the app for review.

You do **not** necessarily need to rebuild the app when the remaining issue concerns store metadata or review information rather than the uploaded binary.

<div align="left"><figure><img src="/files/Gu3tvNMl4WYzxexrCdRK" alt="" width="383"><figcaption></figcaption></figure></div>

### Checking Publishing Status Again

After completing a missing requirement, return to Thunkable and select **Check again**, **Recheck**, or the relevant publishing action.

Thunkable checks the current store configuration again and updates the number of passing requirements.

### Publishing vs. Store Review

Uploading your app and making it publicly available are separate steps.

When Thunkable successfully uploads your build, the store may still need to process the binary and review the app. Apple and Google control their own processing and review timelines.

Therefore, statuses such as **build uploaded** or **store listing synced** do not necessarily mean that the app is already live in the store.

Continue following the instructions shown in the publishing chat and in **App Store Connect** or **Google Play Console** until the store confirms that your app has been submitted, approved, and released.

### Troubleshooting

If **Publish app** is unavailable or the checklist shows incomplete requirements, open each red item and follow the provided action.

If you have completed something in App Store Connect or Google Play Console but Thunkable still shows it as incomplete, use **Recheck** or **Check again** to refresh the validation.

If automated submission fails after the binary has already been uploaded, read the publishing chat carefully before starting another build. In many cases, only additional store information needs to be completed manually.

If your checklist is complete but the app is not yet publicly available, check its status directly in App Store Connect or Google Play Console. Store processing, review, and release can continue after Thunkable has finished uploading the app.
