如何將 Replit 應用程式發佈至 App Store 和 Google Play（2026）

Short answer: first check what Replit built for you. If it's a web app (most Replit Agent projects are), you need to turn it into a native app before the stores will take it. If it's a mobile app built with Expo, you can build and submit it with Expo's tools. Either way, you need developer accounts, a few store requirements Replit doesn't add by default and, on a new personal Google Play account, a 14-day closed test.

Replit makes it easy to go from an idea to a working app. Getting that app into the App Store and Google Play is a separate job, and it trips up a lot of first-time publishers. Here's the full path.

Disclosure: this guide is from LetsDeployIt, where we publish AI-built apps to both stores.

What did Replit build: a web app or a mobile app?

Open your project and look at the files and the preview:

• A web app runs in the browser preview and usually uses React, Vite, Next.js or a Python or Node server. You open it with a URL. This is what most Replit Agent projects are.
• A mobile app uses Expo and React Native. You'll see an app.json or app.config file and expo in package.json, and you preview it on your phone with Expo Go.

The path to the stores depends on which one you have.

Path A: your Replit app is a web app

The App Store and Google Play want native apps, so a web app needs a native version first. You have two options:

• Wrap it: put your website inside a native shell with a tool like Capacitor. It's quick, but Apple often rejects apps that feel like a website in a frame under Guideline 4.2.
• Convert it: rebuild the screens as a React Native and Expo app that talks to the same backend. It takes longer, but it feels like a real app and passes review far more reliably.

Your Replit web app keeps running either way. The store app is a separate build that uses the same data.

Path B: your Replit app uses Expo

If your project is already an Expo app, you're much closer. The usual route is Expo's EAS services, which build your iPhone and Android apps in the cloud and upload them to the stores, with no Mac needed:

npm install -g eas-cli
eas login
eas build:configure
eas build --platform all
eas submit --platform ios
eas submit --platform android

Before building, check app.json has a real app name, an ios.bundleIdentifier and an android.package (like com.yourcompany.yourapp), plus your icon and splash screen.

The Replit-specific traps

These catch Replit apps more than most:

• Your app must call your deployed backend, not the development URL. The URL you see while building is for development. Publish your backend with Replit Deployments and point the mobile app at the deployed .replit.app address (or your own domain), so it keeps working when your workspace isn't open.
• Keep your deployment always available. A store app with a backend that's asleep or stopped looks broken to reviewers. Choose a deployment type that suits real traffic.
• Don't put secret keys in the app. Anything bundled in a mobile app can be read by anyone who downloads it. Keep API keys in Replit Secrets on the server and have the app call your backend.

What the stores require that Replit doesn't add

AI builders focus on making the app work. The stores also expect:

• Account deletion inside the app if people can sign up. How to add it.
• Sign in with Apple next to Google or other social login on iPhone.
• A privacy policy on a public web page.
• Apple's in-app purchase for digital goods and subscriptions.
• A demo account for the reviewer if any part of the app needs a login.

Developer accounts and the Google Play closed test

You'll need an Apple Developer account ($99 a year) and a Google Play developer account ($25 once). If your Google Play account is personal and was created after November 13, 2023, you must run a closed test with at least 12 testers for 14 days in a row before you can publish. Here's how the closed test works. Start it as early as you can.

How long does it take?

For an Expo project with the requirements in place, the App Store can take a few days, mostly review. For a web app, add the time to convert it. On Google Play, the closed test sets the pace, so plan on about three weeks for a new personal account.

FAQ

Can I publish a Replit app directly to the App Store? Only if it's a native mobile app, such as an Expo project. A Replit web app needs a native version first.

Do I need a Mac? Not with Expo's cloud builds.

Will my Replit web app keep working? Yes. The store app is separate and can use the same backend.

Why was my wrapped Replit app rejected? Usually Guideline 4.2: Apple sees it as a website in a frame. Adding native features helps; converting to a native app is the reliable fix.

Conclusion

Publishing a Replit app comes down to three things: a native build, the store requirements, and a backend that's deployed and always on. If you'd rather not handle the conversion and store review yourself, LetsDeployIt converts AI-built apps to native and takes them through both stores until they're approved. See the launch checklist for every requirement in one place.

Stuck on a Replit app right now? Tell us where in the comments.