Help for owners
I have a website or web app and I want it in the app stores
Short answer
There are three routes: a wrapper around your website, a web app packaged for Android, or a proper app built for phones. Apple's review guidelines say an app must offer more than a repackaged website, so a plain wrapper may be refused on the App Store. Decide what the app must do that the site cannot.
Does this sound like your situation?
- My website works well and customers ask for an app.
- A cheap service offered to turn my site into an app in a day, and I am not sure it will be accepted.
- Apple refused my app because it looked like my website.
- I need notifications or offline use, which a website does not do well.
- I want to be in the stores so customers can find me, but I do not want to build everything twice.
Why does this happen?
Apple does not accept a thin wrapper
Apple's guideline 4.2 says apps should include features, content and a UI that elevate them beyond a repackaged website. An app that only shows your site in a frame is at risk of being rejected.
Confirmed by developer.apple.com
Android has a route for web apps
Chrome's documentation describes a Trusted Web Activity, which lets an Android app open your web app content fullscreen. The app and the site are expected to come from the same developer, and the site is verified through Digital Asset Links.
Confirmed by developer.chrome.com
A packaged web app keeps your website's limits
The content still behaves like a website. The host app cannot read the web content's cookies or local storage, which matters when sign-in is shared between the two.
Confirmed by developer.chrome.com
Apps are reviewed as finished products
Apple also says submissions must be final, fully working versions with working URLs, and that if the app has a login you must provide a demo account and keep the backend live for the reviewer.
Confirmed by developer.apple.com
What can I do about it today?
- Write what the app does that the site does notPush notifications, using the camera, working offline, faster repeat tasks. If the list is empty, you may not need an app yet.
- Check who your customers are onSee how many of your visitors use phones and which system. That decides whether you need both stores.
- Make the website work well on a phone firstA responsive site is useful on its own and is the base for any of the three routes.
- Be careful with a one-day conversion serviceAsk them how the app will pass Apple's rule on repackaged websites, and whether you own the store accounts and the code.
- Open the store accounts in your own nameWhichever route you choose, the app should be published from accounts your company controls.
When should I bring someone in?
- Apple has already refused the app for being a website in a wrapper.
- Your site has accounts and payments and you need them to work the same in the app.
- You want one codebase for the site and the apps and do not know if that is realistic.
How do I handle it?
- Find what the app must addI go through your site with you and list which features justify a real app and which can stay on the web.
- Choose between wrapper, packaged web app and native or Flutter appI explain each route in plain words, with what it costs in upkeep and the review risk on each store.
- Reuse what already worksWhere possible the app calls the same backend as your site, so rules, users and data are not duplicated.
- Prepare the store submissionStore listing, demo login for the reviewer, privacy details and screenshots are prepared with the app.
- Hand over the accounts and the codeStores, signing details and the repository are in your name before I finish.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will Apple accept a wrapper around my website?
The guideline says apps need to go beyond a repackaged website. I cannot promise any outcome, because Apple decides each review, so the app should offer real features of its own.
Can the website and the app share one codebase?
Sometimes. It depends on how the site is built. I look at it before suggesting a route.
Is a packaged web app good enough for Android?
It can be, for a web app that is already good on phones. Chrome describes it as an app opening your web content fullscreen.
Do I need both stores?
Only if your customers use both. Start where most of them are.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.