Home / Solutions / Websites and web apps
Turn your existing web app into an iOS and Android app
What I hear
We already have a web app that works, and customers keep asking for it in the App Store and Google Play. We do not want to rebuild everything.
Yes, a working web app can usually be turned into iOS and Android apps without a rewrite. I use Capacitor, which puts your web build inside a native shell and gives it access to device features. The harder part is not the wrapping. It is making the result behave like an app and getting through store review.
How the wrapping works
Per Capacitor’s documentation, you install the core and CLI packages in your project, run npx cap init with an app name and ID, then npx cap add ios and npx cap add android. That generates native projects. A webDir setting in the Capacitor config must point at your web build output (dist, build, www, depending on framework), and after each build you run npx cap sync to copy it across. The native projects are then opened in Xcode and Android Studio, so an iOS build needs a Mac.
A wrong webDir is a common reason for a blank screen, and so is code that assumes a normal browser, like absolute URLs, cookies on another domain, or file downloads that rely on browser behaviour. I go through your app for these.
What makes it feel like an app
- Safe areas, notches and the keyboard covering inputs.
- Navigation: the Android back button, swipe-back on iOS, deep links into specific screens.
- Offline behaviour: at least a clear message and saved drafts instead of a spinner forever.
- Native pieces where they help: push notifications, camera and file pickers, biometric sign-in, share sheets.
- Splash screen and icons in every required size.
Store requirements that catch people out
Apple’s App Review Guidelines say an app should include features, content and UI that elevate it beyond a repackaged website (4.2), require in-app purchase to unlock features or digital content (3.1.1), and require an in-app way to delete an account if the app supports account creation (5.1.1). I build account deletion and a privacy policy link in from the start.
For Google Play, personal accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. Plan for that delay if you use a personal account. Check Google’s current help page for exact wording and any rules for organisation accounts.
When not to wrap
If your product is mostly a content site or a thin dashboard with nothing native in it, a progressive web app or a good mobile site may serve better and avoid review risk. If you need heavy graphics, background location or complex offline sync, a native or cross-platform build is more honest than a wrapper. I will tell you which side your app is on after looking at it.
What I need from you
- Source access to the web app, or the repository if it is mine to wrap.
- Developer accounts created by you: Apple Developer Program and Google Play Console.
- Your app name, icons, screenshots, privacy policy and support contact.
I build test versions for TestFlight and Google Play testing, fix what testers find, submit, and handle review feedback until it is live. Price is fixed and agreed first. Monthly maintenance covers OS updates and store requirement changes.
Sources
- Apple App Store Review Guidelines: https://developer.apple.com/app-store/review/guidelines/
- Google Play Console Help, app testing requirements for new personal accounts: https://support.google.com/googleplay/android-developer/answer/14151465
- Capacitor, getting started: https://capacitorjs.com/docs/getting-started
What it replaces
a full native rebuild for each platform, or customers bookmarking a website
How pricing works
One fixed price, agreed before I start. Optional monthly maintenance after handover.