Replit Mobile Apps: Expo Builds, App Store Steps, No Google Play

Yes, Replit can build a real iPhone app and put it on the App Store. Replit Agent writes a native app with Expo and React Native, runs the server side on Replit, and gives you a QR code so the app opens on your own phone through Expo Go at no cost. Publishing needs your own Apple Developer Program membership; Replit then compiles the binary in the cloud, so you do not need a Mac or Xcode. Android is the gap. Publishing to Google Play is not yet supported^[1], although Android versions can be built and previewed. One more trap: the Replit app on your phone is a tool for building web projects, not the route for shipping yours.

Start with a mobile artifact in the Project Editor

Mobile Apps opened to every Replit user in January 2026. You pick the Mobile app type in the Project Editor at replit.com and describe the app in plain language; Agent then writes the Expo client plus a server that lives on Replit. That server can use the built-in PostgreSQL database, App Storage for files such as profile photos, connectors and AI Integrations, so the result is a full-stack app rather than a screen mockup. Sign-in comes from Clerk Auth, which Agent provisions for you.

One project holds up to seven artifacts, but only one of them can be a mobile app. That limit shapes planning. A web app and a mobile app can live in the same project, sharing one backend and one database, and publishing pushes every artifact at once. A second phone app, though, needs a second project. Projects created before Agent 4 arrived in March 2026 need a one-time update before they can hold a mobile artifact alongside the original web app.

A free Starter account is enough to start a mobile project and preview it. The catch is the build mode: Starter works in Lite build only, the quick-edit experience, while Full build, Plan Mode, connectors and AI Integrations need Core or higher. On the free Starter plan you can publish one app, and its link goes down after 30 days unless you publish it again, so a phone app's backend needs a paid plan to stay up. For a phone app with a real backend, that gate arrives early. Our guide to whether Replit is free lists everything Starter covers and where it stops.

Preview on your own phone before paying anyone

Early testing costs nothing. Install Expo Go, a free app from the App Store or Google Play, scan the QR code Replit shows, and your app opens on the phone without a native build. On Core, Pro and Enterprise you also get streamed iOS Simulator and Android Emulator previews inside the Project Editor^[2]. Those streams work in Chrome, Safari and Chromium-based browsers, not in Firefox. Core costs $20 per month billed monthly or $18 per month billed annually.

Expo Go has blind spots. It runs your code inside a shared preview app, so iOS push notifications, in-app purchases and Sign in with Apple do not work there; each needs a real build installed from TestFlight. Hardware features such as the camera, haptics and GPS call for a physical phone rather than a simulator. Android is friendlier for notifications, since push can be tested in Expo Go on an Android device. A sensible split: check screens, flows and data in Expo Go, then leave Apple-controlled features for TestFlight.

Privacy during testing is limited too. Replit's Enterprise documentation notes that private previews are not supported for mobile apps in Expo Go, in the simulators or in the Replit mobile app, even where an organization requires private development URLs. Treat a shared preview as something other people could open, and keep real customer data out of it until the production database and the published backend are in place.

Set up the Apple side before you press Launch

Apple sets this gate, not Replit. You need an Apple Developer Program membership before uploading anything, even a build you only want to share privately. The membership carries an annual fee paid to Apple, requires two-factor authentication, and approval usually takes about a day. Individuals verify with a government ID. An organization verifies the business itself and needs a D-U-N-S number, so a company account involves more paperwork than a personal one and is worth starting early.

Replit's upload tool, called Launch, signs in with the Apple account enrolled in the program; Replit says it uses those credentials only to authenticate with Apple and does not store the password. Launch then picks a valid distribution certificate and provisioning profile, or creates new ones when none exist. The build compiles on Expo's servers, which is why no Mac is involved, and Replit submits the result to App Store Connect. EAS CLI and EAS Build are not supported on Replit, so developers used to Expo's own tooling should expect Replit's guided flow instead.

From TestFlight to a live App Store listing

The sequence below follows Replit's publishing docs, and the order matters, because each step depends on the one before it and Apple's reviews sit between your build and your customers:

1. Publish the web app and API backend first, because the phone app calls them.
2. Run Launch. A build can take up to 45 minutes, and builds queue at peak times^[3].
3. Let internal testers install right away, or send the build to an external TestFlight group after Apple's Beta App Review, usually about a day for the first build.
4. Submit for App Store review. Apple often answers in a day or two, longer for a new app, and rejections come with notes.

The bundle ID is permanent. Whatever ID the first App Store publish uses stays tied to that Replit project; if Agent changes it, the next publish fails until the change is undone. Moving to a new ID means a remix or a fresh project, which creates a separate App Store Connect app without the old listing, TestFlight builds or reviews. TestFlight builds also expire after 90 days, so a long beta needs fresh builds submitted along the way.

Apple's rules travel with the app. If people can create accounts in it, they must be able to delete the account inside the app; signing out or deactivating does not count. Apps with shared content need filtering, reporting and blocking tools. When the app offers another social login such as Google, iOS also requires Sign in with Apple, and the Clerk setup keeps separate provider lists for development and production. Replit recommends an Agent security scan before sharing a build, while noting that the scan is neither an Apple approval nor a guarantee of security.

Charging money inside the app

Digital purchases on a phone follow the store's rules. For in-app subscriptions Replit relies on RevenueCat, whose integration became generally available in March 2026. Apple and Google require their own in-app purchase systems for digital content, and both take a cut of each sale^[4]. Stripe stays on the web side: Replit points web apps to Stripe and native mobile subscriptions to RevenueCat. Shopify covers physical goods, and Whop handles digital products sold through a web app.

Real money moves late. Previews run RevenueCat in test mode with no charges, and real charges start only after Apple approves the app for distribution. Syncing RevenueCat with App Store Connect needs the paid developer membership, a submitted app, a connected bank account and a signed Paid Apps Agreement. Because purchases cannot run in Expo Go, the payment flow gets its first real check in a TestFlight build, which is one more reason to reach TestFlight well before your launch date.

Android, the Replit phone app and the running bill

The Play Store is different. You can build an Android version and preview it in the emulator or in Expo Go, but Replit's docs state that publishing to Google Play is not yet supported. In February 2026 Replit named better Android publishing as upcoming work. If a Play Store listing is a launch requirement, Base44 produces store files for both Apple and Google from its Builder plan upward, as a wrapper around the published web app rather than a native build; our Replit vs Base44 comparison sets the two approaches side by side. Lovable has no native or store output at all.

Do not mistake the Replit app on your phone for a publishing tool. The Replit iOS app is for building websites and web apps with Agent, dictating prompts and getting alerts when Agent finishes or needs help. It cannot create, preview, build or submit native mobile apps; that work happens in the Project Editor at replit.com, with the Android app offering native work only where supported. Use it to follow Agent's progress away from your desk. Ship from the browser.

Running costs belong to the owner. The client runs on the phone, but its server, database and AI calls run on Replit, so their usage comes out of your monthly credits and then pay-as-you-go unless you set a budget. A budget is a hard cap: once reached, Replit temporarily suspends all usage-based services, hosting included, which leaves the phone app without its backend. The Replit pricing guide explains credits, budgets and plan options.

The bottom line

Replit is a workable route to a native iPhone app for a builder without a Mac. Agent writes the Expo code and the backend, Expo Go gives free previews, and Launch handles certificates and the upload. Plan for Apple's membership and review times, fix the bundle ID before the first publish, and test payments and notifications in TestFlight. If Google Play matters on day one, Replit does not support publishing there yet, so plan a separate Android route or choose a builder that produces Play Store files.