How do I get my AI-built web app into the Apple App Store?

By Ranjit Bhinge, founder of Blur Studio · Updated · 6 min read

Short answer: You have three routes: let people install your web app from the browser (a PWA, which is a web app that can sit on the home screen), wrap it in a thin native shell with a tool such as Capacitor, or rebuild it as a true native or React Native app. Wrapping is the usual choice for a Lovable, Bolt or Replit app, but Apple's rules say an app must be more than a repackaged website. You also need a $99 a year Apple Developer account, a Mac or a cloud build service, and one or two native features that justify the app.

Ranjit Bhinge

You built a web app with an AI tool such as Lovable, Bolt or Replit, and now customers are asking for it in the App Store.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Lovable, Bolt and Replit are AI tools that build a working app from a plain-language description. For the three of them this guide assumes the result is a web app. The App Store only takes native apps, so something has to bridge the gap. This page explains the three routes, what Apple checks, what it costs and how long it takes, and how to decide whether you need the App Store at all.

First: do you need the App Store?

Ask this before spending money. Many apps do not need it. Customers who find your app through a link or a QR code can use it in the browser. If the main reason is "it would look more professional", the PWA route below may be enough. If the reason is push notifications, app-store search, a camera or file features, or customers who simply will not use anything that is not in the store, then continue.

Three routes compared

RouteWhat it isRough effortPick it when
PWA (home screen web app)Your web app with an icon on the home screen. Not in the App StoreDaysExisting customers, simple use, no store needed
Wrapper (Capacitor and similar)Your web app inside a thin native shell, submitted to the storeRoughly 2 to 6 weeks in my estimate, mostly store setup and reviewThe web app works well and you need a store listing plus a few native features
Native or React Native rebuildThe app rebuilt so it runs as a true mobile appMonthsHeavy phone features, offline use, or a mobile-first product

The effort figures are my own planning estimates, not published numbers, and they vary with how clean your app is. Treat them as a way to compare routes.

Route 1: the PWA

A PWA is a web app people can install from the browser. The web.dev guide explains that iOS has no install prompt: the user adds it by hand from the browser's share menu. You should add an apple-touch-icon or the home screen icon becomes a screenshot. It also lists limits on iOS: only the standalone display mode, no support for badging or app shortcuts, and each installation of the same PWA has its own isolated storage. It is free and fast, but it is not in the App Store and many customers will never find it.

Route 2: the wrapper

Capacitor is an open-source tool that puts your built web app inside a native iOS project. Its docs describe it as a native runtime that lets your JavaScript talk to native Swift code, using Apple's WKWebView to display your pages. You add it to your project, run npx cap add ios to generate the iOS project, npx cap sync to copy your built site into it, and open it in Xcode, Apple's developer app. The docs list requirements for building: a built web folder with an index.html, and a current Xcode.

Capacitor needs the code, so first get it into a repository you own. Check how your builder exports or syncs code, since the options differ by tool and plan. How to move an AI-built app to production covers that step, and if you are stuck on the build side, see how to hire a Bolt developer or hire a Replit developer.

Expo is a different path, aimed at React Native apps. Its EAS Submit service uploads an iOS build to App Store Connect and works from macOS, Linux or Windows, so you do not need a Mac for that step. It needs a paid Apple Developer account, a bundle identifier, and a production build, which you can make with Expo's build service, on your own computer or with Xcode. That suits an app built in React Native, not a plain web app.

What Apple checks

This is where wrapped web apps fail. Apple's App Review Guidelines say:

  • Guideline 4.2, Minimum Functionality: your app should include features, content and UI that elevate it beyond a repackaged website. If it is not "app-like", it does not belong on the store.
  • Guideline 2.1, App Completeness: submit a final version with all metadata and working URLs. Placeholder text, empty websites and crashes are rejected.
  • Guideline 5.1.1, Privacy: you must link a privacy policy in App Store Connect and inside the app. If people can create an account in the app, you must also let them delete the account inside the app.
  • Guideline 4.2.6, Template apps: apps made from a commercial template or app generation service are rejected unless the content provider submits them directly. My reading is that this targets services that submit apps on behalf of clients, which is different from a wrapper you build and submit yourself, but read the full text.

Practical meaning: a wrapped site with nothing native, no sign of being built for a phone, is at risk under 4.2. Adding a few things a website cannot do well, such as push notifications, camera access or a proper offline screen, helps, as long as they are useful and not decoration. Always read the current guidelines page, because Apple updates it. If you were already rejected, see what to do when an AI-built app is rejected.

Costs

  • Apple Developer Program: US $99 per membership year, per Apple's program page. Waivers exist for some nonprofits, schools and government bodies.
  • Apple's commission: Apple's page says the App Store commission on digital goods and services is 30%, or 15% for qualifying small businesses and partner programs and for qualifying subscriptions. If you sell digital content in the app, this affects your pricing.
  • A Mac or a cloud build service: Xcode runs on a Mac. If you have no Mac, a cloud build service or Expo's build tools can do it, for a fee.
  • Developer time: the real cost. For ranges, see AI app development cost.
  • Designing the store page: screenshots, description, icon and a support page.

A realistic timeline (estimate)

  1. Days 1 to 3: decide the route, create the Apple Developer account (enrolment can take time to approve, so start early).
  2. Week 1: get the code into a repository you own, make sure the web app is stable on a phone screen.
  3. Weeks 1 to 2: wrap it, add the native pieces, privacy policy, account deletion if you have accounts.
  4. Weeks 2 to 3: test on real devices through TestFlight, Apple's tool for beta testing.
  5. Weeks 3 to 4: submit and answer any reviewer questions. A first rejection is common, so allow for a second round.

These dates are my planning estimate for a clean app. A messy app takes longer.

Review prep checklist

  • App works on at least two real iPhone sizes, with no horizontal scrolling or tiny text.
  • No placeholder text, no "coming soon" pages, no broken links.
  • Privacy policy linked in the store listing and inside the app.
  • Account deletion available inside the app, if people can sign up.
  • A demo login for the reviewer in the review notes, if the app needs one.
  • At least one thing that feels like an app and not a website.
  • Every payment for digital goods follows Apple's rules. Check the guidelines before choosing how to charge.
  • No secrets in the code, and the backend is locked down. See whether your AI-built app is production ready.

Who should not do this yet

If the web app still changes every week, if the login is unfinished, or if you cannot say who will fix it when something breaks, wait. A store release is slower to change than a website, because each update goes through review. Fix the web app first.

How I'd approach this

I would start with the PWA, because it costs almost nothing and tells you whether customers use the app from their phones at all. If they do, and the store still matters, I would use a wrapper and spend the effort on the two or three native touches that make the app feel real, not on trying to wrap everything. I would also fix security and account basics before submitting, since Apple's reviewers and your own customers will both find the gaps.

I would only go native from scratch if the product depends on the phone itself. For most small business apps built in Lovable, Bolt or Replit, a clean wrapper on a solid backend is enough. Get the code into your own repository first, since every later step needs it.

Questions people ask

Can I publish a Lovable or Bolt app directly to the App Store?

Not as it is. They build web apps, and the store takes native apps, so you wrap the app (for example with Capacitor) or rebuild it. First get the code into a repository you own using how to move an AI-built app to production.

How much does it cost to put an app on the App Store?

Apple charges $99 per membership year for the Developer Program. The larger cost is developer time to wrap or rebuild the app and prepare the store listing. See AI app development cost for build ranges.

Will Apple reject a wrapped website?

It can. Guideline 4.2 says your app should go beyond a repackaged website. Add real native features that help users, and make sure the app works well on a phone. If you are rejected, read what to do when an AI-built app is rejected.

Do I need a Mac to submit an app?

Xcode runs on a Mac, and Flutter's and Capacitor's iOS routes rely on it. Expo's EAS Submit service says it works from macOS, Linux or Windows for the upload step. Cloud build services can also do the build for you.

Is a PWA good enough?

For existing customers who open a link, often yes. On iOS users add it by hand from the share menu, and some features, such as badging and app shortcuts, are not available. It is not listed in the App Store.

Do I need a privacy policy and account deletion?

Yes. Apple's guidelines require a privacy policy link in App Store Connect and inside the app, and if your app lets people create an account it must also let them delete it from inside the app. Ask a lawyer to review the policy if you handle sensitive data.

More in this topic: Problem solving: AI-built and no-code apps (26 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…