To ship a Replit app to the App Store and Google Play, first move it from the development workspace to a stable Replit deployment or other production hosting, then package the deployed URL in a native iOS and Android shell, or build an Expo project if Replit generated a React Native app. The most common problems are development URLs, cold starts and secrets handling, all of which should be fixed before review.
On this page
Replit Agent can take a description and turn it into a running full-stack application, with a server, a database and a public URL, all inside the Replit workspace. That speed is exactly why many Replit apps are not ready for the stores when their owners first try. The workspace is a development environment, and an app that works there may sleep, change URLs or expose configuration once real users arrive. This guide focuses on the production steps that are specific to Replit and then on the packaging and store process.
From workspace to production deployment
A Replit project has a development URL that is tied to the running workspace and a separate deployment URL once you publish it through Replit's deployment options. Never put the development URL into a mobile app. It can change, stop when the workspace stops and show development tooling. Create a deployment, connect your own domain and use that domain everywhere: in the app shell, in authentication redirect settings and in email links.
Choose the deployment type with mobile usage in mind. Replit offers different deployment models, such as autoscaling deployments that scale down when idle and deployments with reserved capacity, plus static hosting for frontend-only apps. At the time of writing, check Replit's documentation for current options and their behavior. Deployments that scale to zero can cause a slow first request after idle periods, which inside an app looks like a frozen white screen. If your app is used intermittently, either choose an always-on option or make sure the native shell shows a loading indicator and the frontend is served as static files while the API warms up.
Secrets, database and security
Replit Agent stores API keys in the Secrets tool when it works correctly, but prototypes often accumulate shortcuts: keys in client-side code, admin endpoints without authentication, permissive CORS rules or a development database used in production. Before you package the app, review where every key is used and make sure only server-side code accesses it. Separate development and production databases, so that experiments in the workspace do not touch real users' data. Add rate limiting to endpoints that call paid AI APIs, because a mobile app with many users can turn an unprotected endpoint into a large bill.
Web app or Expo app
Replit can generate classic web apps and, increasingly, mobile projects built with Expo and React Native. Check what you have. For a web app, the fastest route to the stores is a native shell that loads your deployed URL and adds native features. You can configure it yourself with WebViewGold, which supports push notifications, biometric authentication, in-app purchases, deep links and an offline screen, or you can have We Set Up Your WebView App configure everything and deliver your personal iOS and Android apps within 72 hours, with an App Store and Google Play approval guarantee or money back.
For an Expo project, you build native binaries with Expo's build tooling or locally, configure bundle identifiers, permissions and icons in the Expo config and submit the builds. This route gives you native UI components but requires more mobile-specific maintenance. The trade-offs are the same as for other builders, which we compare in turning a Lovable project into native iOS and Android apps.
Release plan for both stores
- Create a production deployment with a custom domain and confirm uptime and response times from a phone on mobile data.
- Move secrets server-side, separate the production database and add rate limits to AI endpoints.
- Add account deletion, a privacy policy page and a public deletion request page for Google Play.
- Package the app with a native shell or build the Expo project, and enable native features that fit your users.
- Register an Apple Developer Program membership (USD 99 per year) and a Google Play developer account (one-time USD 25), ideally as an organization.
- Test with TestFlight and a Google Play testing track; new personal Play accounts currently need a closed test with at least 12 testers for 14 days.
- Complete listings, Apple's App Privacy answers and Google's Data safety form, then submit with a demo account and clear review notes.
Review risks specific to Replit apps
Reviewers often encounter Replit apps that load slowly on first open, which is usually the cold start problem described above. Others show a generic landing page as the first screen, or include developer elements such as debug panels and test routes. Some fail because the reviewer's demo account was created in the development database, not in production. Test the submitted build exactly as the reviewer will: fresh install, mobile network, production URL, demo credentials. Our overview of common rejection reasons for AI-built apps lists further checks, and the guide to Google Play closed testing explains the tester period.
Running the app after launch
Once live, your Replit deployment is production infrastructure. Monitor uptime and errors, keep backups of the database, and decide how changes move from the workspace to the deployment, ideally with a short manual test before each redeploy, since the mobile app updates as soon as the deployment does. If usage grows to the point where you need dedicated infrastructure, a proper CI pipeline or a team, that is a sign the app is becoming a business; turning that kind of project into an operating product is where our company building work starts.
Frequently asked questions
Can I use my Replit development URL in a mobile app?
No. Development URLs depend on the running workspace and can change or stop. Use a Replit deployment or other production hosting with your own domain.
Why does my Replit app show a white screen when opened?
Often the deployment scaled down while idle and the first request takes time to start it. Use an always-on deployment option or serve the frontend statically with a loading state.
Can Replit build native mobile apps?
Replit can generate Expo and React Native projects as well as web apps. Web apps reach the stores through a native shell, while Expo projects are compiled into native builds.