Skip to content

Answers use only the pages of this documentation, and every answer links to the pages it came from. Your question is sent to our answering service to be answered, and kept so the people who write these pages can see what readers ask.

Publish to Google Play

How to build your app file for uploading to Google Play

Ada builds the file for you to download and upload to Google Play yourself.


If you don’t have one, sign up at the Google Play Console. Google charges a one-time fee and verifies your identity before you can publish.


A Package Name is your app’s permanent, unique name in the store, commonly written backward like a web address: com.yourcompany.yourapp.

After your app goes live in Google Play, its Package Name can’t change, so pick it carefully.

  1. In the left panel, click App Settings.
  2. Under Android Settings, enter your Package Name. It can be the same as your iOS one.
  3. Click Save settings.

  1. In the left panel, click Publish.
  2. Open the Android section.
  3. Under Build Format, choose:
    • AAB: for Google Play. Choose this to publish.
    • APK: to install the app directly on an Android phone for testing.
  4. Click Build AAB. Each step shows in the build row while it runs. Most builds take several minutes.
  5. When the row says Built, click the download icon (Download build). The download link works for one hour. To get a fresh link after that, click the icon again.

Ada signs your app with a signing key it creates for your app and keeps for you. You don’t need to make or upload one.


You can’t install an AAB file directly on a phone. Instead, Google Play gives you testing tracks: stages where a small group of people install and test your app before everyone can. You “promote” a release from one track to the next, and finally to Production, the public Google Play Store.

  • Internal testing: Share your app with up to 100 testers for quick checks. Your app and store listing don’t need to be finished.
  • Closed testing: Share your app with a larger group of testers you invite by email.
  • Open testing: Anyone can find your test on Google Play and join it. Make sure your store listing is ready before you use this track.
  • Production: Your app is live for everyone on Google Play.

You don’t have to use every track. You can promote a release from Internal testing straight to Production. We recommend you ALWAYS test before pushing to Production.


Warning

🛑 Important: After you create your app in Play Console, never change its Bundle ID (package name) in Ada. Google Play treats a different package name as a completely different app.

  1. Click All apps, then click Create app.
  2. Enter your App name (the name people see in Google Play), choose the Default language, choose App or Game, and choose Free or Paid.
  3. Accept the Declarations, then click Create app. Play Console opens your app’s dashboard.

Google requires information about your app’s content, like its privacy policy, ads, and target audience, before you can release it on any track.

  1. In Play Console’s left menu, click App content. It’s near the bottom of the menu. You can also search for it in the search box.
  2. For each section, click Start, answer the questions, and click Save.
  3. Click the back arrow to return to App content, and repeat until every section is done.

  1. In Play Console’s left menu, go to Test and release > Testing > Internal testing.
  2. Click Create new release.
  3. If Play Console asks how to sign your app, choose to let Google create and manage your app signing key. Ada signs every build with your app’s upload key, and Google uses its own key for the copy people download.
  4. Under App bundles, click Upload and choose the AAB file you downloaded from Ada.
  5. Check the Release name. Play Console fills it in from your build, and only you can see it. Optional: Add Release notes about new features or fixes.
  6. Click Next, review any errors or warnings, then click Save and publish (or Start rollout to Internal testing). Some warnings are normal for Adalo apps and don’t block your release.

  1. On the Internal testing page, click the Testers tab.
  2. Click Create email list and give the list a name.
  3. Add your testers’ email addresses one at a time, or upload a CSV file. Add your own email address too.
  4. Click Save changes, then click Create. Email lists are shared across all your apps.
  5. Make sure your new list is selected.
  6. Optional: Enter a feedback URL or email address for testers.
  7. Click Save changes.
  8. Under How testers join your test, click Copy link and send the link to your testers.

Each tester opens the link on their Android phone, accepts the invitation, then installs your app from Google Play.


After you’ve tested a release, promote it to the next track, or skip ahead to Production.

  1. On the page for the track your release is in, find the release and click Promote release.
  2. Choose the track to promote it to.
  3. For every track above Internal testing, including Production, choose where your app is available:
    1. On the new track’s page, click the Countries / regions tab.
    2. Click Add countries / regions, select the countries, and click Add.
  4. If the new track is Closed or Open testing, add testers to it the same way as in Add testers.
  5. Click Next, then click Save and publish. Google reviews the release before testers can get it.

Before your app goes to Production, fill in what people see on your Google Play page. Most fields are required, so gather your text and images before you start. Check out Adalo Studio for assistance with your listing!

  1. In Play Console’s left menu, go to Grow users > Store presence > Store listings, then open your main store listing.
  2. Enter your App name, Short description, and Full description.
  3. Upload your App icon and Feature graphic.
  4. Upload at least 3 Phone screenshots that show your app in use, not your login or welcome screens.
  5. Upload Tablet screenshots: at least 1 for each tablet size. One way to make screenshots is to take screen captures of your app in Ada’s preview.
  6. Click Save.

  1. Find the release you tested, click Promote release, and choose Production. If your account has to apply for Production first, see the note on new personal accounts in Understand testing tracks.
  2. On the Production page, click the Countries / regions tab and add the countries where your app is available.
  3. Click Next, review any errors or warnings, then click Save and publish (or Start rollout to Production).

Google reviews your app before it goes live. Reviews usually take a few days but can take longer. If Google rejects your app, you get an email with the reason and what to change.


When your app is already in Google Play, you release a new version the same way:

  1. In Ada, build a new AAB and download it.
  2. In Play Console, create a new release on Internal testing (or straight on Production), upload the AAB, and roll it out.
  3. Promote the release through your tracks to Production.

Ada raises your app’s version code with every build, so Google Play accepts each new file. If Google Play says the version code was already used, see Troubleshooting.

For more about testing tracks, see Google’s Set up an open, closed, or internal test.