Skip to content

Web to app

How to get your web app, PWA or no-code app into the app stores

Can a web app, PWA, Bubble or Glide app go in the App Store? What Apple's 4.2 rule allows, wrapper vs native, and what Google Play needs.

By Arshad Mehmood, co-founderPublished 4 min read

On this page

Key takeaways

  • Apple's App Store only accepts app builds, and a website in a frame risks rejection under guideline 4.2, Minimum Functionality.
  • The four routes are wrap the site, publish a PWA (Google Play only, as a Trusted Web Activity), build a companion app on your API, or rebuild natively.
  • A companion app on your existing API is the route least likely to hit 4.2, and it needs no new backend.
  • Every route still needs developer accounts ($99 a year for Apple, $25 once for Google), a privacy policy, account deletion and a reviewer demo login.
  • FlutterFlow produces Flutter code that can already be built for both stores, so it may need store work rather than a rebuild.

Yes, you can get a web app into the App Store and Google Play, but not as a plain website. Apple only accepts app builds, and a site in a frame risks rejection under guideline 4.2. You have four routes: wrap the site, package it as a PWA (Google Play only), build a companion app on your existing API, or rebuild it as a native app. The right one depends on how much your users will do on their phones.

What the stores accept

Apple reviews every app against the App Review Guidelines. The rule that matters most here is 4.2, Minimum Functionality: "Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or 'app-like,' it doesn't belong on the App Store."

That doesn't ban web technology inside apps. It means a reviewer will ask what your app does that your website doesn't.

Google Play has its own minimum functionality policy: "We do not allow apps that only have limited functionality and content" (Play Console help). Google Play also accepts PWAs packaged as a Trusted Web Activity, which opens your site full-screen inside an Android app.

Every route still needs the same store paperwork: developer accounts ($99 a year for Apple, $25 once for Google), a privacy policy, in-app account deletion if users can sign up, Google's Data safety form and a demo login for reviewers. New personal Google Play accounts also need a closed test with at least 12 testers for 14 days (Play Console help; more in the 12 testers rule).

Option 1: Wrap your web app

A wrapper is a small native app that loads your website in a WebView. Tools such as Capacitor, or paid wrapper services, do the packaging.

Good for: content sites, internal tools, a first presence in the stores while you plan something bigger.

Watch out for: Apple's 4.2. A wrapper that only shows your site is the classic rejection. Wrappers do better when they add things a website can't easily do: push messages, offline content, camera or biometric login, native navigation. Even then, approval isn't guaranteed. Login screens, payments and slow pages also feel worse inside a wrapper than in the browser.

Option 2: A PWA

A progressive web app installs from the browser to the home screen, with an icon and offline support. On Android you can also publish it to Google Play as a Trusted Web Activity. On iPhone, a PWA lives on the home screen through Safari, not in the App Store.

Good for: products where people mostly want a shortcut, and where being in Apple's store doesn't matter.

Watch out for: discovery. Some customers will only look for you in the App Store, and a PWA isn't there.

Option 3: A companion app on your API

If your web product already has an API (most SaaS products do), a native mobile app can use it directly. You don't rebuild the backend. You build the screens mobile users actually need, such as checking status, approving, booking, messaging and getting notified, and leave the heavy admin work on the web.

This is the route least likely to hit 4.2, because the app is a real native app with its own UI. It's what PerceptiaAI's Companion App is: a mobile app on your existing product's API, at $3,490 or $6,500. There's no new backend, which is why it costs less than a full build.

Option 4: Rebuild as a native app

For no-code products (Bubble, FlutterFlow, Glide, Adalo), the tool may limit what you can publish, what it costs to run and who owns the result. A rebuild turns it into a code app you own, with your data moved across. PerceptiaAI's Move to Code does this at the Starter ($3,990) or Growth ($7,500) price.

Check your tool first. FlutterFlow, for example, produces Flutter code that can already be built for both stores, so you may need store work rather than a rebuild.

Compare the four routes

RouteTypical costStore riskWhat users get
WrapperLowest: a freelance wrap or a wrapper subscriptionHigh on Apple if it adds nothing to the siteYour website in an app icon
PWALittle, if your site is already a PWANo Apple listing; Google via Trusted Web ActivityA home-screen shortcut, some offline use
Companion appPerceptiaAI: $3,490 or $6,500Low: a real native appNative screens for mobile jobs, on your current data
Rebuild (Move to Code)PerceptiaAI: $3,990 or $7,500LowA full native app you own outright

On timing: a Starter build takes about 4–6 weeks and a Growth build about 8–12, from the start payment to submission to both stores. Apple and Google review time comes on top.

Already wrapped and stuck?

If you have a wrapped or no-code build that works but hasn't made it through review, you may not need a new app. PerceptiaAI's Store Launch ($1,190 or $1,990) packages a working app for both stores, fixes launch-blocking bugs, runs a safety pass and adds Apple and Google must-haves such as account deletion and Sign in with Apple. If it was rejected under 4.2, start with what the rejection means and our post on guideline 4.2.

Built your product with an AI tool such as Lovable or Replit? The steps are similar, with a few extra checks: see AI-built app to the app stores.

Before you submit any route

  • Apple and Google developer accounts in your company's name
  • Privacy policy linked in the listing and inside the app
  • In-app account deletion, plus a web deletion link for Google
  • Data safety form and Apple privacy labels filled in to match the app
  • A demo login with sample data for reviewers
  • Real app features beyond the website, if you wrap
  • A 12-tester closed test plan if you use a new personal Google account
  • Store screenshots, icon and description

The full list, step by step, is in the app launch checklist.

For an App Check and what can follow it, with prices, see the concept app: Deskhaus, a rejected app rebuilt and relaunched. For a phone app built on top of an existing web product, with the same logins and data, see Countwise, a stock-control companion app.

Questions people ask

Can I put a PWA on the App Store?

Not directly. Apple's App Store takes native app builds, so a PWA has to be packaged inside an app first, and then it is reviewed like any other app, including the minimum functionality rule. Google Play can accept a PWA packaged as a Trusted Web Activity.

Will Apple reject a wrapped website?

It can. Apple's guideline 4.2 asks for features, content and UI that elevate an app beyond a repackaged website. A wrapper that adds real app features has a better chance than one that only shows the site.

Do I need a new backend for a mobile app?

Usually not. If your web product already has an API, a native app can use it, so your data, users and business logic stay in one place.

Can I publish a Bubble, Glide or FlutterFlow app to the stores?

It depends on the tool. FlutterFlow produces Flutter code that can be built for both stores; other tools offer wrappers or their own mobile builders. Check your tool's current publishing docs, then judge the result against Apple's 4.2 rule.