By Israr Kundi · Published 2026-11-12
How to Convert Your Website into a Mobile App
How to convert your website into a mobile app? You have three routes: a progressive web app, a WebView wrapper, or a real rebuild — and the plain wrapper is the one most likely to be rejected.
The problem: "I already have a website, I just want it as an app"
You run a shop or a small business. Your website already works, and customers keep asking for an app. Online tools promise to turn your site into an app.
So you pay and submit the app. Then a rejection can arrive, naming Apple's Guideline 4.2.
The cause: the stores want an app, not a bookmark
Apple's App Review Guidelines, updated in October 2026, open Guideline 4.2 with this sentence: "Your app should include features, content, and UI that elevate it beyond a repackaged website." An app that is not particularly useful, unique, or "app-like" does not belong on the App Store.
Two smaller rules catch wrappers too. Rule 4.2.2 says apps should not be mainly marketing material, adverts, web clippings, content aggregators, or a collection of links — unless they are catalogues. Rule 4.2.6 says apps made with a commercial template or app generation service will be rejected unless the provider of the app's content submits them. So submit under your own Apple Developer account, not the converter's.
Google Play's rules read differently. Its Spam policy does not allow apps whose primary purpose is to "drive affiliate traffic to a website or provide a webview of a website without permission from the website owner or administrator" — owning the site covers that part. Its Functionality policy is the harder one: apps that "do not have the basic degree of adequate utility as mobile apps" are not allowed.
WebViews themselves are not banned: plenty of approved apps show some screens in one. The problem is an app that is only the same website a user could open in Safari.
One more rule: since 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36) or higher.
The minimum fix: how to convert your website into a mobile app the stores accept
1. List what the app must do that the website cannot
Push notifications, offline access, camera upload, barcode scanning, fingerprint login, saved items. If the list is empty, you do not need a store app yet — a bookmark or a progressive web app does the same job with no store fee and no review.
2. Pick one of the three routes
Start light: a progressive web app installs from your website, works offline, and skips store review. It cannot be listed on the App Store, but Android lists it in Google Play through a Trusted Web Activity.
The middle route is a WebView wrapper, loading your site inside a thin app shell. It is quick to build, and it stands a better chance with real app features added — push, offline support, native navigation, device features, native screens for the main tasks — though neither store publishes a checklist for passing. Budget for one or two review rounds.
Choose a rebuild in Flutter for the third route: one codebase, real apps on iOS and Android, native screens from the start. A rebuild is built as an app from the start. Pick it when customers will open the app weekly or daily for a core task, like ordering or booking. My starting price for a small 4–5 screen app with Supabase is from $300; publishing to one store is $100.
3. If you keep the wrapper, add app-only features before you submit
Add a native tab bar and keep web content to single screens. Add push notifications and a usable offline screen. Keep login signed in, and make file upload work inside the app. In your App Review notes, name the features only the app has, and give reviewers a demo account.
4. Submit under your own accounts, with the current targets
Apple charges $99 a year for its Developer Program, Google a $25 one-time registration fee, for any app listed in the stores. Publish under your own accounts, and check the build targets Android 16 for Google Play.
What NOT to do: do not submit a bare wrapper of your homepage — the rules above are written about exactly that app. Do not let a converter service submit the app under its own account — rule 4.2.6 rejects that. Do not wrap a website you do not own. And do not treat a rejection as final: Apple sends the reason and guideline number, so fix that point and resubmit.
When to get help instead of converting it yourself
When the app takes payments or holds user accounts, get a developer to plan the app-only features with you before you pay anyone. If you already got a Guideline 4.2 rejection, get help before you resubmit.
If this is your app, contact me through https://israr-kundi.web.app
Free · 15 minutes
Stuck on a half-built app?
Send me the app link or a short description. In a free 15-minute rescue audit, I'll tell you the most likely launch blockers and the practical next step.
Request a free rescue audit