User Guide
Before you publish your first app
Required Assets
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
To publish your app on Android, you'll need to add of access the following in your Thunkable project's App Settings:
App Name
Icon
Package Name (referred to as App (Bundle) ID in Thunkable)
Version Name & Version Code
Package Name
Every new Thunkable project is automatically given a unique App (Bundle) ID. For the purposes of publishing to the Play Store, this is refered to as your app's package name.
To locate your package name:
Open your Thunkable project.
Navigate to the Design tab.
Click the Settings gear icon in the sidebar.
Copy the content of the App (Bundle) ID field. This is your package name.
You'll notice that Thunkable adheres to the following naming convention to avoid conflicts with other apps: com.yourDomainName.yourAppName. It is all lower case letters, none of the segments begin with a number, and there are no characteres with accents.
Each time you create a new app
Set your Android Version
Google Play requires each new version of your app to have a unique and sequentially higher Version Name and Version Code. You can let Thunkable auto-increment (or automatically increase) the version data for you.
Download your Android App Bundle (AAB) file
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.
An AAB file cannot be installed on an Android device. If you want to download and install your project, please read the Download docs.
To download your Android App Bundle (AAB) file:
Within your Thunkable project, click the Publish and Download icon.
A publishing modal is provided to guide you through the publication process.
Enter the email address you want the app download link sent to.
Click Send.
In approximately 30 minutes, you will receive your AAB file to the email address you provided.
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.
Create a new app on the Google Play Console
Sign-in to your Google Play Console account.
Click Create app in the upper right.
Complete the requested app details fields. Note: The App Name is how your app will appear on Google Play.
Complete the required declarations.
Click Create app.
Manage your app signing
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.
In Thunkable:
Download your Keystore Zip
You will need to download your Keystore Zip. This is a compressed version of your app's Android Keystore.
You can download this from your project settings under Keystore Zip:
We recommend creating a new folder on your computer. Download your AAB file and your Keystore Zip to this new folder. That way, the correct AAB file and Keystore Zip will be together.
In the Play Store:
Click Manage App Signing:
Click Export and upload a key from Java keystore:
You can skip straight to Step 3: Upload generated ZIP and Upload the Keystore ZIP you downloaded from your project settings.
Click Continue.
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 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.
Click View tasks in the Set up your app section to see the tasks you must complete.
Click on a task.
Complete the required fields.
Click Save.
Click Dashboard above the task name in the upper left.
Repeat with the remaining tasks in the list.
Apps that request access to sensitive permissions or data (as defined in the user data policies) 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
Click Main store listing under the Grow heading in the sidebar.
Complete the required fields and upload the required assets. See here for additional guidance: Add preview assets to showcase your app.
Click Save.
Create and publish a release
Return to the Google Play Console Dashboard.
Click View tasks in the Create and publish a release section to see the tasks you must complete.
Click the Select countries task.
Identify the countries you want your app to be available in.
Click Create a new release.
Upload the AAB file into the App bundles section. Instructions for downloading your AAB are available here: Download your Android App Bundle (AAB) file
Add Release notes for this update.
Click Next.
To update your app
Updating an existing app on the Play Store
In your Google Play Console, click on the Releases tab.
Click the Create New Release Button
Upload the AAB file into the App bundles section. Instructions for downloading your AAB are available here: Download your Android App Bundle (AAB) file.
Add a Release name so you can identify this release. It isn't shown to users on Google Play.
Add Release notes. Let users know what's in your release.
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)
the same keystore as the published app
You will not need to change any app signing settings when updating a published app.
Last updated