Convert Replit to an iOS App: Expo Route or Web Wrapper (2026)

Key takeaways

Since January 2026, Replit builds native iOS apps with Expo and publishes them via TestFlight – but mobile apps start as new projects, not conversions of your web app.
Wrapping your existing Replit web app keeps one codebase; it needs a custom domain, a deployment without cold-start blanks and real native features.
Replit's docs say Google sign-in doesn't work in in-app webviews: plan email and password, Sign in with Apple and a native Google flow for wrapped apps.
Digital goods sold through Stripe or Whop on the web need In-App Purchase on iOS – RevenueCat in Replit's Expo apps, StoreKit through WebViewGold in a wrapper.

Our recommended solution

Turn your Replit app into a real iOS app with WebViewGold

WebViewGold wraps the Replit web app you already have in a native Xcode project and adds push notifications, a native offline screen, deep links, a QR scanner and more – the native value reviewers at the App Store look for. Built by our own team, and we submit WebViewGold apps all the time.

Get WebViewGold How it helps ↓

Can you convert a Replit app to an iOS app?

Yes, though "convert" means one of two things. To convert Replit to an iOS app, you either build a new mobile project in Replit – Agent writes TypeScript, Expo and React Native turn it into a native app, and Replit publishes it to TestFlight and the App Store – or you wrap the web app you've already published on Replit in a native iOS shell. Replit doesn't transform an existing web project into a mobile one.

That last point surprises many builders. Replit launched native mobile apps on January 15, 2026, and the discussion around the launch made clear that existing web apps aren't converted: mobile apps start as new mobile projects. Replit's own tip for an Agent that builds a web app by mistake is to "start again and select Mobile app as the app type before building".

And Apple isn't blocking Replit-built apps. Its 2026 dispute with Replit concerned the Replit iOS app running generated apps inside itself, and Replit shipped its first iOS update in four months on May 15, 2026. If your app was flagged under the Developer Code of Conduct, read our article on Replit apps and Guideline 5.6.

What your Replit project brings to the App Store

A Replit web app built by Agent is full-stack: a frontend, a backend server, a built-in database and storage. Each part shapes the iOS project:

Hosting. Static deployments aren't compatible with Agent-built apps, so yours runs on Autoscale – the default, which scales to zero when idle – or on an always-on Reserved VM, at a replit.app address or your custom domain.
Sign-in. Clerk is the default auth system on the Starter, Core and Pro plans, with email and password plus Google, GitHub, Apple and X as social providers. Replit Auth, the alternative, signs users in with Replit accounts.
Payments. Stripe and Whop handle web checkouts; RevenueCat handles in-app subscriptions in native mobile apps.
Code. You can download the project as a zip or sync it both ways with GitHub, so the code is yours to move.

A Replit mobile project keeps that server on Replit and adds an Expo app that runs natively on the phone. Whichever route you take, the iPhone app depends on a Replit deployment that is always reachable and behaves the same for every user.

Want your Replit app in the App Store without the trial and error?

Book a free consultation call: we check your web app, tell you which native features it needs and what to fix before review. Or hand it off – our App Specialists set up signing and CI/CD, prepare the store listing and submit the app for you.

Free consultation call Book our service →

Replit's Expo route, a WebViewGold wrapper, Capacitor or a PWA?

If this sounds like you	Best fit	Trade-off
You're starting fresh, or the app lives on the phone – trackers, field tools, booking flows	A new Replit mobile project (Expo)	You rebuild the screens; Replit publishes to the App Store only, not Google Play; EAS CLI and dev builds aren't supported on Replit
You have a working Replit web app with users and want the same features on iPhone	WebViewGold wrapper around the published deployment	Needs native value for Guideline 4.2 and a deployment that is always ready
You're a developer and want parts of the frontend inside the app bundle	Capacitor with your exported code	Agent-built apps are full-stack, so you bundle only the frontend and call your Replit API; Capacitor's docs say loading a live URL via `server.url` is not intended for production
You don't need App Store distribution	A PWA from your existing app	No official Replit PWA documentation; Home Screen web apps get web push since iOS 16.4; no App Store listing

For most Replit builders, the first two rows are the real choice. If your web app already has users and features, wrapping keeps one codebase and ships fastest. If you're early, or the experience should feel fully native, Replit's mobile route is worth the rebuild.

Route 1: publish a new Replit mobile project to the App Store

Start a mobile project. On the Replit home screen, describe one phone-first flow and select Mobile app as the app type.
Preview on a real iPhone. Scan the QR code to open the app in Expo Go; on Core, Pro and Enterprise plans you can also use the iOS Simulator in the Project Editor. Camera, push notifications, haptics and GPS need a real phone.
Add sign-in and monetization. Clerk handles accounts. Replit's own guide adds Sign in with Apple on iOS when Google is offered and reminds you to enable providers in Production. In-app subscriptions run through RevenueCat, which Agent sets up with a paywall and a test mode.
Launch from the Publishing tab. Start publishing to the App Store and Replit opens Launch, an Expo flow embedded in Replit. Sign in with your Apple Developer account – two-factor authentication is required – and confirm the app name and bundle ID, which can't be changed after the first build.
Let Replit build and upload. Replit configures the certificates, builds the app in the cloud and submits it to App Store Connect for TestFlight beta review.
Finish in App Store Connect. Add screenshots, description, age rating, App Privacy details and review notes, then submit the version for review.

Native changes such as a new icon or permission need a new store build. Replit previews with Expo Go, which only supports modules included in the Expo SDK; anything beyond that needs dev builds, which – like EAS CLI and EAS Build – aren't supported on Replit.

The shortcut from Replit to the App Store

WebViewGold: your Replit app, native on iOS

Instead of building native features from scratch, start from WebViewGold. You get ready-made Xcode and Android Studio projects for your website, with native modules you switch on in the configuration:

Push notificationsOneSignal or Firebase, for real, personal events
Native offline screenNo browser error pages when the connection drops
Native splash screenApp-like start instead of a loading web page
Deep linksLinks open the right screen inside the app
QR & barcode scannerDevice features the website alone can't offer
In-app purchasesNative purchase flows where the store requires them

No tool guarantees an approval: Apple still judges what your app offers. Use the native features in your main user journey – our App Specialists review your WebViewGold app before it goes to the App Store.

Discover WebViewGold Let us submit your WebViewGold app

Route 2: wrap your published Replit web app with WebViewGold

WebViewGold, built by our own team, is a ready-made Xcode project that turns anything running in Safari – Replit apps included – into a native iOS app. Set it up so the Replit side doesn't trip review:

Publish for an app audience. Connect your custom domain, keep access public and choose a Reserved VM, or stay on Autoscale and rely on a native loading state while an idle deployment wakes up. Never wrap a Starter-plan deployment: it goes down automatically after 30 days and carries a "Made with Replit" badge whose removal requires Core.
Enter the URL in Config.swift. Use the custom domain, never a replit.dev development URL, and set a custom user agent so your web app can adapt its layout inside the wrapper.
Fix sign-in for an app. Replit's docs are plain: "Google sign-in does not work in embedded browsers or in-app webviews." The robust fix is native – ASWebAuthenticationSession or Google's Sign-In SDK added to the Xcode project. The quick one: offer Clerk's email and password plus Sign in with Apple, which WebViewGold handles automatically, and keep Google on the website. Avoid sending users to Safari to sign in – Apple's account deletion guidance calls linking out to the default browser for sign-in a poor experience under Guideline 4. Use your own OAuth credentials in production so consent screens show your name, not Replit's.
Add native value. Push via OneSignal, Firebase or Pushwoosh, Face ID, a QR scanner, native navigation, the offline screen with Reconnect and Apple's native rating dialog are switchable modules.
Handle digital purchases. Stripe or Whop checkouts that unlock digital content need In-App Purchase on iOS; WebViewGold's StoreKit module requires the Extended license. Physical goods and services can keep Stripe.
Add account deletion. Guideline 5.1.1(v) requires deletion inside the app when users can sign up – ask Agent for a delete-account flow that removes the Clerk user and their data.
Build and test. Archive in Xcode or use the separately sold Cloud Builder, then test through TestFlight on an iPhone and an iPad against the production deployment.

One advantage over no-code builders: your Replit app is code you control, so serving the apple-app-site-association file for universal links is a small server change rather than a platform limitation.

Getting a Replit app through App Review

Review account. Create it on the published app – Clerk's development and production user stores are separate – verify its email and unlock paid features.
App Privacy details. Cover Clerk account data, payments through Stripe or RevenueCat, analytics and anything your AI features send out. Guideline 5.1.2(i) requires you to "clearly disclose where personal data will be shared with third parties, including with third-party AI, and obtain explicit permission before doing so".
Screenshots. Replit can turn real screenshots into polished marketing images; keep them faithful to what the app does.
Review notes. Every feature, where it lives, which parts are native, and the demo login.

Guideline	Typical Replit trigger	Read more
4.2 Minimum Functionality	A wrapper that only frames the web app	4.2 for WebView apps
2.1 App Completeness	A blank cold start; a demo login that only exists in development	2.1 for WebView apps
4.8 Login Services	Google, GitHub or X sign-in without Sign in with Apple	4.8 for WebView apps
3.1.1 In-App Purchase	A Stripe or Whop checkout for digital access	3.1.1 for WebView apps
2.5.2 Software Requirements	Features that change after review without a new build	2.5.2 for WebView apps
5.6 Code of Conduct	Private deployments, development URLs, Agent changes during review	Replit and Guideline 5.6

The pre-submission check in appsubmitter.io's iOS service – AI-powered, then reviewed by an App Specialist – walks through exactly these points before your build reaches App Review.

Who does what: Replit, WebViewGold and appsubmitter.io

On the Expo route, Replit builds and uploads; on the wrapper route, WebViewGold gives you the native project. What remains in both cases is the part that decides the review: signing and CI/CD for the Xcode project, the App Store Connect listing, App Privacy details, review notes, the submission and the conversation with App Review.

That is what appsubmitter.io does – AI-powered pre-submission checks plus an App Specialist, in your own Apple Developer account with our team working as members of it, which is also what Guideline 4.2.6 expects. Code changes, such as a native Google sign-in, are quoted separately upfront. Book the iOS service or talk through your Replit project in a free consultation call. Going to Google Play as well? Continue with Replit to Android.

Checklist before you submit

You decided between a new Replit mobile project and a wrapper around your existing web app.
The web app runs on your custom domain with public access – no replit.dev URL, no Starter-plan deployment.
Cold starts can't show a blank screen, thanks to a Reserved VM or a native loading state.
Google sign-in never runs inside the WebView; email and password plus Sign in with Apple work in the app.
Sign-in providers shown in the app are enabled in production, with your own OAuth credentials.
Digital purchases use In-App Purchase via RevenueCat or StoreKit; Stripe and Whop never unlock digital content in the iOS app.
Users can delete their account inside the app.
App Privacy details cover Clerk, payments, analytics and any data sent to AI services.
The review account exists in production and unlocks every feature.
The build was tested through TestFlight on an iPhone and an iPad.

Frequently asked questions

Can I convert my existing Replit web app into an iOS app?

Not inside Replit – its mobile apps start as new mobile projects. What you can do is wrap the published web app in a native shell: WebViewGold, made by our team, loads your custom domain and adds push, Face ID, an offline screen and in-app purchases, so you keep one codebase. Rebuilding as a Replit mobile project makes sense when the app should be fully native.

Do I need a Mac to publish a Replit app on the App Store?

Not on Replit's mobile route: Replit and Expo manage the build in the cloud, and Replit's docs answer the question with a plain "No". For a wrapped web app, you need Xcode on a Mac or WebViewGold's Cloud Builder, which configures, builds and uploads the app in the browser. Either way, you need an Apple Developer Program membership.

Is Apple blocking apps built with Replit?

No. In 2026, Apple held back updates of Replit's own iOS app because it ran generated apps inside itself, which conflicts with Guideline 2.5.2; Replit shipped an update again in May 2026. Apps built with Replit go through normal App Review and are judged like any other app – on functionality, completeness, payments, sign-in and honest behavior.

Can I update the app without going through App Review again?

Partly. In a wrapped app, everything you publish on Replit appears immediately, which is fine for content and fixes; new features should ship with a new build and review notes. In a Replit mobile app, server-side changes reach users directly, while native changes such as icons or permissions need a new store build. Keep what users see consistent with what App Review approved.

How long does App Review take for a Replit app?

Apple says it typically reviews at least 50% of submissions within 24 hours and 90% within 48 hours. External TestFlight testers also need a Beta App Review, which Replit's docs put at about a day for the first build. Plan extra rounds in case App Review asks questions or rejects the first version.

Should I choose Replit's Expo route or WebViewGold?

Choose the Expo route if you're starting fresh or want a fully native interface and can live with its limits – Expo Go-compatible modules and no Google Play publishing from Replit. Choose WebViewGold if your Replit web app already works and has users: you keep one codebase, add native features and can ship the same web app on iOS and Android.

Sources and further reading

Store policies and third-party products change regularly – always check the current versions. This article is independent advice and not affiliated with or endorsed by Apple, Google or any other company or product mentioned; all trademarks belong to their owners. WebViewGold and appsubmitter.io are made by our team at jocapps GmbH.

Convert Replit to an iOS App: Publish a Replit Mobile Project or Wrap Your Existing Web App