How to Publish a Replit App to Google Play (The Part Replit Skips)

Publishing a Replit app to the Apple App Store is almost a button. Replit hands you to a wizard, the wizard handles Apple, and you are done. For Google Play there is no button. Replit does not guide you through Android at all, so you create and submit the release yourself.

That sounds worse than it is. The Android path is more manual, but it is not hard, it does not need a Mac, and most of the real work is done by the same cloud service that builds your iOS app. This guide is the part Replit leaves out.

If you want the Apple side, we cover it separately in how to publish a Replit app to the App Store. This one is Google Play only.

The short version

• Replit’s Publish button ships your app to the web, not to Google Play. There is no Android store button in Replit.
• You build the Android app with EAS, Expo’s cloud build service. The command eas build --platform android produces a signed .aab, the file Google Play needs.
• EAS generates and stores the signing key for you, so no Android Studio and no keytool. It all runs in the cloud from Windows or Linux.
• You need a Google Play developer account, which is $25 once, not a yearly fee.
• Then the real wall: if your account is personal and created after 13 November 2023, you must run closed testing with 12 testers for 14 continuous days before you can go to production.
• Watch the track. eas submit defaults to internal testing, and internal testing does not count toward that 12 testers requirement.

First, make sure you have a mobile app

The same check that applies to the App Store applies here. A Replit Mobile project gives you a React Native app on Expo, which is what this guide builds from. A Website project gives you a web app, which is a different and riskier road onto the store.

The quick test: if your project previews on your phone through Expo Go, it is a mobile app and everything below fits. If it only opens in a browser, skip to the section on web apps near the end, because Google judges those differently.

Why there is no Replit button for Android

It is worth understanding the shape of this before you start. Replit’s built-in publishing flow for stores targets Apple. The wizard it opens even says “Targeting the App Store” as its first step. There is no Android equivalent yet.

So for Google Play you step outside Replit and drive the build yourself. The tool you use, EAS, is the same one that builds the iOS app behind Replit’s wizard, so you are not learning a whole new system, just running it directly.

Step 1: Build a signed app bundle with EAS

Everything here happens in the cloud. Nothing compiles on your machine.

Configure the project. Run eas build:configure. This creates an eas.json file next to your package.json, which holds your build and submit settings.

Build for Android. Run eas build --platform android. It queues a cloud build that takes roughly 10 to 15 minutes, and you can watch progress on the Expo dashboard. What comes back is an Android App Bundle, the .aab file, and it is already signed. The default production profile produces exactly this.

Two things worth knowing here:

• Google Play requires new apps to be published as app bundles, not APKs. If you configure the build to output an APK instead, Google Play will not accept it on a release track.
• EAS generates and stores your Android keystore, so you never run keytool and never open Android Studio. This is the step that historically scared people off Android publishing, and the tooling removes it.

Step 2: Set up your app in Google Play Console

Register a Google Play developer account if you do not have one. It costs $25 once, and unlike Apple’s yearly fee, you never pay it again. Do this early, because the registration and identity checks take time you will not want to spend on submission day.

In Play Console, create your app entry: the name, the default language, and whether it is an app or a game. This is also where your store listing lives, the description, screenshots, and the privacy policy link that Google requires.

Step 3: Get your bundle onto Play

Once your app exists in Play Console, you can upload the bundle. Run eas submit --platform android. For this to work, EAS needs a Google Service Account key, a JSON file that lets EAS submit on your behalf. You set that up once and reference it in your submit settings.

Here is the trap that costs people days. By default, eas submit lands your build on the internal testing track. Internal testing is handy for a quick check with a few people, but it is not closed testing, and only closed testing counts toward the requirement in the next step. If you leave the track on its default, you will finish the upload feeling done and then discover the 14-day clock has not even started. Set the track deliberately.

Also check your target API level while you are here. From 31 August 2026, new apps and updates must target API 36 to be published. A build on an older level is blocked at upload, so confirm it before you start a release rather than on the day.

Step 4: The 12 testers wall

You have a signed bundle, it is uploaded, and you assume you are nearly there. You are not, and this is the stage where most Android launches stall.

If your Google Play developer account is a personal account created after 13 November 2023, you must run a closed test with at least 12 testers who stay opted in for 14 continuous days before you can apply for production access. Organisation accounts and older personal accounts are exempt.

Three details decide whether those 14 days actually count:

• Testers must opt in through the official Play opt-in link. Sideloading the app to a friend does nothing.
• The days must be continuous. If your opted-in count drops below 12, the clock can reset rather than pause.
• Testers who install and never open the app are the quiet killer. Google looks at engagement, not just installs.

Building the app was the fun part. Finding twelve strangers who will keep it installed and opened for two weeks is the part that traps people, especially when you do not have an audience yet. We explain the reasoning behind the rule in why Google Play requires 12 testers, and the fastest legitimate way to meet it in our guide to getting 12 testers. This is also exactly the gap Testers Community exists to fill: real developers test each other’s apps and stay opted in for the full 14 days.

What if you built a web app, not a mobile app?

Then you are wrapping a website, and it helps to know what Google actually objects to, because the rumours are stricter than the rule.

The policy people quote says Google does not allow apps whose primary purpose is to drive affiliate traffic to a website, or to provide a webview of a website without permission from the website owner. If it is your own app and your own site, that specific clause is not aimed at you.

The rule that will actually catch you is minimum functionality. Google does not allow apps with only limited functionality and content, and expects apps to have a basic degree of adequate utility as mobile apps. The risk is not that your app uses a webview. The risk is that it is thin. An app that does something real and behaves like an app will generally be fine, while a login screen wrapped around a single page will struggle.

Google is more forgiving here than Apple, which rejects repackaged websites outright. So if you have a web app, Google Play is the more realistic first target.

What it costs

• Google Play developer account: $25, one time, never renewed.
• Apple Developer Program, for comparison: $99 every year.
• Replit and Expo: both have free tiers that will get a first app built and submitted.

If you are choosing where to launch first, the maths favours Google. A one-time $25 versus a recurring $99, and no Mac required either way.

Common questions

1. Does Replit publish my app to Google Play?

No. Replit’s Publish button deploys your app to the web at a .replit.app address, and its built-in store wizard targets only the Apple App Store. For Google Play you build and submit the Android release yourself using EAS, Expo’s cloud build service.

2. What file does Google Play need from a Replit app?

An Android App Bundle, the .aab file. Google Play requires new apps to be published as app bundles rather than APKs. Running eas build for the Android platform with the default production profile produces one, already signed with a keystore that EAS generates and stores for you.

3. Can I publish a Replit app to Google Play without a Mac or Android Studio?

Yes. EAS builds run in Expo’s cloud, so nothing compiles on your machine and you never open Android Studio. It works from Windows and Linux. You need a $25 Google Play developer account, but no local build tools and no Apple hardware.

4. Do I still need 12 testers if my app was built on Replit?

Yes. The requirement is tied to your Google Play developer account, not to how the app was built. If it is a personal account created after 13 November 2023, you need 12 testers opted in for 14 continuous days of closed testing before you can apply for production access. How you built the app makes no difference.

5. Why did my Replit app land in internal testing instead of closed testing?

Because eas submit defaults to the internal testing track, and internal testing is not closed testing. Only closed testing counts toward the 12 testers for 14 days requirement. Set the track deliberately in your submit settings, and check in Play Console which track your build actually landed on.

6. How much does it cost to publish a Replit app on Google Play?

A Google Play developer account is a one-time $25 fee, with no renewal. Replit and Expo both have free tiers that cover building and submitting a first app. That makes Google Play cheaper to start on than the App Store, which charges $99 every year.

7. What target API level does my app need in 2026?

From 31 August 2026, new apps and app updates must target API 36 to be published on Google Play. If your build targets an older level, the upload is blocked. Check this before you start a release cycle rather than on submission day.

The order that actually works

1. Build it on Replit and test it on a real phone with Expo Go.
2. Register your Google Play developer account early, because the $25 and the identity checks take time.
3. Build a signed .aab with EAS, and confirm it is an app bundle, not an APK.
4. Create your app in Play Console and submit the bundle, setting the track to closed testing rather than the internal default.
5. Start the 14 days of closed testing immediately, so the clock runs in the background while you finish your store listing.
6. Apply for production access once the 14 days are genuinely complete.

The build is the part everyone worries about, and it is now the easy part. The part that decides whether your Replit app ships on Google Play is the fortnight of closed testing at the end, which is exactly where Testers Community comes in.