Turn your web app into native iOS and Android apps — from the repository you already have

A wrapper (Capacitor, or a service built on it) puts your web app inside a native shell so it can go in the stores. It is the fastest route and the right one when the website is the product. It is still a web page: navigation, gestures and new device layouts are whatever the web app does, and Apple’s guideline 4.2 sets the bar — “Your app should include features, content, and UI that elevate it beyond a repackaged website.”

Web to native produces a different thing: native apps whose screens are built from the platform’s own parts, that follow platform updates first, that an iOS or Android engineer can open, and that talk to the same backend as your web app. The web app keeps running as the web product. Convert a web app to a mobile app compares the routes if you are not sure which you need.

1. Connect the repository. Sign in with GitHub and pick the repo. Modaal reads the route tree, the data model, the API calls and the auth provider. It does not need your web app to be built in any particular tool.

2. Read the plan. Before any code, you get a document: the screen list (from your routes), the features, what maps to what, what the phone app will do differently from the web app, and what is out of scope. This is the same document a developer would write after reading your repo. Edit it, then approve it.

3. The agents rebuild, feature by feature. Each feature’s logic is written once; the iPhone app renders it in SwiftUI and the Android app in Jetpack Compose — from Modaal’s documentation, “Each feature’s logic — its state, the actions that change it, the effects it requests — is written once.” The screens are re-created for the phone from the plan, not translated from CSS. The API, the auth and the data are the ones your web app uses; with Supabase, the iPhone app uses Supabase’s own Swift client and the Android app the community-maintained Kotlin client.

4. Test on a real phone. Builds run locally on your Mac with your Xcode; TestFlight and Play testing tracks for the people you want to try it. You review each feature as it lands, and the plan for the next one.

5. Submit from your own accounts. Apple Developer Program ($99 a year) and Google Play Console ($25 once), opened in your name; Modaal uploads to them. The Xcode and Android Studio projects stay on your disk, on every plan.

Carries over: the backend, the database, the users, the auth provider, the API contract, the business rules (re-implemented in the new language, unchanged in meaning), the route tree as the screen list, design tokens as values.

Rebuilt natively: every screen, the navigation, the state handling per screen, layout, and anything that used browser APIs or web-only libraries. Convert a React app to a native mobile app has the layer-by-layer table for React and Next.js codebases.

A founder or product person with a validated web product and users asking for the phone app. A team whose web app is the product and whose phone app needs things the web can’t do well — camera, offline, notifications that open the right screen, widgets, a subscription through the store. Anyone who was about to hire a developer to “convert” the app and wants to see the plan first. Not for a website that only needs an icon and notifications: the wrapper route is shorter for that, and turn a website into an app explains it.

The Xcode project and the Android Studio project on your own disk from the first feature, on the Free plan too. Your own store accounts as the publisher. Your own backend under your own credentials. Your own AI agent — Claude, Cursor, Codex and others — on the subscription you already pay for, so there are no credits and no per-token markup. Code export vs no-code lock-in lists the six things a builder can hold hostage; here, none of them are held. The Free plan covers one project with unlimited prompts on one platform; Pro is €9 per user per month billed annually, €15 monthly, and adds both platforms, TestFlight distribution and Git collaboration — /pricing.