Classic Docs


To publish your app on the Play Store from Thunkable, please follow the steps below:

1 / Set up

Here are the minimum requirements for publishing to the Google Play Store:
  • Google Play Developer account ($25 one-time registration fee)
  • Assets
    • App icon at 512 px by 512 px
    • Feature graphic at 1024 px by 500 px
    • Screenshots

2 / Version your app

Every app you publish must have aVersionCodeand aVersionName. You can set these in the designer under the properties panel for theScreen1component.
VersionCodeis an integer value that will not be visible to Google Play Store users. It is used by other apps to check if your app has been upgraded or downgraded. It defaults to 1 and should be increased by one with every successive change whether it is a major change or a minor change.
VersionNameis a String which can be anything you would like. It is defaulted to1.0. A common structure is a decimal number which is increased by 1 for every major change and0.1for every minor change. For example, an initialVersionNamecould be1.0which can be updated to1.1after a small change and2.0after a larger change.
You will need to increase theVersionCodeand change theVersionNameof your application when you upload a new version to the Play Store.

3 / Download app (.apk) to your computer

Package the app (.apk file) by going to the "Export" menu on the Thunkable toolbar
Select "App (save .apk to my computer)." A pop-up box (seen below) should alert you that your download has begun. Note: The other option (provide QR code for .apk) produces a scannable QR code that will download the app for two hours. You can share this code with others, but they have to use it within 2 hours of your generating it.
You can also download the apk directly from your apps home page by clicking on the download arrow next to any app project.

4 / Upload to Google Play

You can now go to Google Play Publishing Home and follow the steps to publish your app to Google Play.

5 / Package name

The package name for all apps built completely on Thunkable:
Currently, there is no way to customize your package name (which is visible on the Google Play store url)

6 / Keystores

During the .apk building process your application is signed with a digital private key which is associated with your account. Whenever you build a new version this same key is used to sign the new version. When an android phone has an application installed on it, it remembers the key that was used to sign it. In order to install an updated version of an application, the new application must be signed by the same key. It is therefore important that you not lose this key!
Your private digital key is stored in a keystore file. Normally the Thunkable server will create this file when needed and store it for you so you do not need to worry about it. Although we do not anticipate losing your keystore file, we recommend that you back it up. From the designer under the "Projects" menu there is a choice labeled "Export Keystore". Select this option. This will download your keystore file to your local computer. Save it in a safe place. It should not be publicly readable as your private digital key is a secret which should not be shared.
If you move your project to another Thunkable server, you will want to upload your keystore to that server (you will see that under "Projects" there is a "Import Keystore" option as well). You only need to do this if you are publishing .apk files to Google Play or if you intend to share your application with other people in general.
IF YOUR keyfile IS LOST OR DELETED IT CANNOT BE RECOVERED. If you were to lose your project's source code, you could always re-enter it from scratch (this may be a lot of work, but is something you can do). NEITHER YOU NOR THUNKABLE CAN RECOVER A LOST keyfile. NO AMOUNT OF EFFORT WILL RECOVER IT, SO BE SURE TO BACK IT UP!!!