# Getting an AI-built app through App Store review

> Built an app with Lovable, Replit or Base44 and want it in the App Store? First check whether it's a web app or a mobile app. What Apple's rules say.

Canonical: https://simondziak.com/writing/ai-built-app-app-store-review
Last updated: 2026-11-20

[Writing](https://simondziak.com/writing)

Published Nov 20, 2026 9 min read No Polish version yet

In short

If you built an app with Lovable, Replit or Base44 and want it in the App Store, the first question is whether what you have is a web app or a mobile app. A web app can’t go into the App Store as it is: it gets there inside a wrapper, a small app that shows your website inside it, or rebuilt as a mobile app, and Apple can reject a wrapper that only shows the website. If your users are happy opening it at its web address, you can keep it as a web app, which needs no App Store review. At App369, having a web app taken into the store for you starts with a paid consultation, $100 per 15 minutes, then a written quote with a fixed price. A rejection under Apple’s Guideline 4.2 starts with the same paid consultation, with a written quote if the change needs building, and a rejection for something in the build, cause unknown, starts with a $450 Diagnosis.

I founded Workspace369 and App369 and benefit from both businesses.

If you asked me how to get the app you built with an AI tool into the App Store, I wouldn’t start with Apple’s rules. I’d start with a plainer question: what kind of app is it? Everything after that depends on the answer, and it’s a part you can check yourself.

## Web app or mobile app: a check you can run

This assumes there is a version of the app you can open outside the tool’s own editor. If it has only ever run inside the editor, go to “If you can’t tell”. You don’t need to read any code.

1. **List every way there is to open it on a phone.** A web address that someone types or taps is one way. An app installed on the phone is another.
2. **Sort it by that list.** If the only way to open it is a web address in a browser, it’s a web app, even if you saved that address as a shortcut on your phone. If there is an app installed on the phone, from the App Store or from a test version the tool helped you put on an iPhone, it’s a mobile app, even if it also has a web version.

**If it’s a web app.** It can’t go into the App Store as it is. A web app opens in a browser at a web address, and it reaches the App Store in one of two ways: inside a wrapper, a small app that shows your website inside it, or rebuilt as a mobile app. Either one goes through App Store review. Next, read “Does it need to be in the App Store at all?” below; if it does, the paths at the end say where each one starts.

**If it’s a mobile app.** It goes through App Store review like any other app. That tells you which rules to read, not whether Apple will approve it. If the app you installed is your web app inside a wrapper, Guideline 4.2 is the one to read first, because its first sentence is about “a repackaged website”. If you haven’t submitted it yet, read the three guidelines below against your app, then submit it from your own Apple developer account. If Apple rejects it, the rejection names a guideline, and the paths at the end say where each kind starts.

**If you can’t tell.** Someone else may have set it up, or it may only have run inside the tool’s editor so far. Ask whoever set it up whether there is an iPhone app, and look in the tool for a way to put the app on an iPhone that isn’t a web address. If you find one, follow the mobile app result. If you don’t, start from the web app result as a working guess, not a finding, and say you couldn’t tell in your first message to anyone you ask for help.

## Does it need to be in the App Store at all?

Before any of this, ask what the store listing is for. If your users are happy opening the app at its web address, you can keep it as a web app. That’s an honest answer, not a lesser one, and a web app needs no App Store review.

A store listing is worth the work when your users expect to find you in the App Store, or the app needs to do something on the phone that the browser version doesn’t. If neither is true for you, keeping the web app is the decision, and the rest of this essay is for later. A listing has a cost of its own too: App369’s route page gives the yearly fee for the Apple developer account it goes out under.

## What Apple’s guidelines say

Three lines in Apple’s App Review Guidelines are the ones I’d read first for an app built this way. I quote them as written, so you can read the rest in context on Apple’s page.

**[Guideline 4.2, Minimum Functionality](https://developer.apple.com/app-store/review/guidelines/#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.”

**[Guideline 4.2.6](https://developer.apple.com/app-store/review/guidelines/#4.2.6):** “Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences.”

**[Guideline 5.1.1(v)](https://developer.apple.com/app-store/review/guidelines/#data-collection-and-storage):** “If your app supports account creation, you must also offer account deletion within the app.”

What I take from those three: Apple expects a wrapper to do more than show the website. Guideline 4.2.6, as written, is about who submits the app: the service, or the provider of the app’s content, which I read as you. Whether a given tool counts as an app generation service is Apple’s call, so submit it from your own Apple developer account either way, in your name or your company’s; App369’s route page says the same. And if people can sign up, they need a way to delete their account inside the app. Approval is Apple’s decision, and nothing on this list guarantees it.

_Source: [Apple, App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/), last updated October 16, 2026. Read November 20, 2026._

## What a rejection means

If Apple has already said no, read the rejection before you change anything. App369’s rejection page puts it this way: “App Store and Google Play rejections fall into two kinds: a gap in the build or the listing that you can fix and resubmit, and a product decision the store disagrees with.”

The first kind has a cause you can find: a reviewer who couldn’t sign in, a build that crashed on their device, account deletion missing from the app. The second kind isn’t a bug. A rejection under Guideline 4.2 means Apple sees the app as a repackaged website, or as not useful or app-like enough. The second half can apply to a mobile app that never was a website. The change is to what the app does, not a bug fix.

## What I do about it at App369

App369 is my app development business in Miami, and I do all the work myself. I also build and run [Workspace369](https://app369.com/case-studies/workspace369/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review), my own product, which is live on the web and the App Store. In the AI-built apps I rescue, an App Store rejection is one of the fixes I make most often. Each path below says who it’s for and what it ends in.

**Not submitted yet, and you want the web app in the store.** [The route from a web app to the App Store](https://app369.com/fix/lovable-bolt-web-app-to-app-store/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review) is written up step by step if you want to do it yourself; building the iPhone version needs a Mac. To have it done for you, the route page says: “It starts with a paid consultation to go through the app and agree what the iOS version needs, such as sign-in and native features. You then get a written quote with a fixed price, and the work goes ahead only with your yes.” [Consultations](https://app369.com/service/consultations/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review) are $100 per 15 minutes, paid upfront.

**Rejected under Guideline 4.2.** App369’s rejection page says that “can mean changing the product itself. That starts with a paid consultation to agree what to change”. The consultation is the same $100 per 15 minutes, paid upfront. If the change needs building, you then get a written quote with a fixed price. [The Guideline 4.2 page](https://app369.com/fix/app-store-guideline-4-2-minimum-functionality/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review) explains what that kind of change looks like.

**Rejected for something in the build.** If the cause is unknown, the [App Fix Ticket](https://app369.com/fixed-price/app-store-rejection-fix/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review) starts with a $450 Diagnosis, in 3 business days from when you send access to the code and the steps that reproduce the problem: the root cause with evidence, plus a fixed repair quote. The Fix is then $750, because the $450 is credited: $1,200 in all. If you already know the cause, the Fix without a Diagnosis is $1,200. The Fix takes 5 business days, counted, like the Diagnosis, from access to the code and the steps that reproduce the problem. It fixes one scoped problem and arrives as a pull request with a test that checks the fix keeps working. A pull request is a change to your code that you review and merge yourself; then you build the app again and resubmit it. Its “Not included” list is new features, rewrites, guaranteed app store approval and production data edits: approval stays Apple’s decision. Not sure your app is a kind it covers? Check fit by email before you pay; the link is on that page.

**A mobile app built from the start**, rather than a wrapper around the web app you have: App369 builds [mobile apps](https://app369.com/service/mobile-apps/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review) from $9,000, quoted in writing.

_Prices as shown on app369.com on November 20, 2026._

## Frequently asked questions

### Can I put an app I built with Lovable, Replit or Base44 in the App Store?

If what you built is a web app, it can’t go into the App Store as it is. A web app opens in a browser at a web address, and it reaches the App Store inside a wrapper, a small app that shows your website inside it, or rebuilt as a mobile app. Apple’s Guideline 4.2 (App Review Guidelines, last updated October 16, 2026) asks for “features, content, and UI that elevate it beyond a repackaged website”, so a wrapper that only shows the website can be rejected. If the tool built you a mobile app instead, it goes through App Store review like any other app. At App369, having a web app taken into the store for you starts with a paid consultation, $100 per 15 minutes, then a written quote with a fixed price.

### How do I tell whether my AI-built app is a web app or a mobile app?

If the only way to open it is a web address in a browser, it’s a web app, even if you saved that address as a shortcut on your phone. If there is an app installed on the phone, from the App Store or from a test version the tool helped you put on an iPhone, it’s a mobile app, even if it also has a web version, and it goes through App Store review like any other app. If that installed app is your web app inside a wrapper, Apple’s Guideline 4.2 is the one to read first. If you can’t tell, ask whoever set it up whether there is an iPhone app; if nobody can point to one, start from the web app result as a working guess.

### Whose Apple developer account should an AI-built app go out from?

Your own, in your name or your company’s. Apple’s Guideline 4.2.6 (App Review Guidelines, last updated October 16, 2026) says: “Apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app’s content. These services should not submit apps on behalf of their clients and should offer tools that let their clients create customized, innovative apps that provide unique customer experiences.” Whether a given tool counts as an app generation service is Apple’s call, so I’d have the app go out from your own Apple developer account either way, as the provider of the app’s content.

### What should I do if Apple rejected my AI-built app?

Read which guideline the rejection names. A rejection for something in the build, such as a crash or a missing account-deletion option, can be fixed and resubmitted; at App369 the App Fix Ticket starts with a $450 Diagnosis when the cause is unknown, and the Fix on its own is $1,200 when you already know it. A rejection under Guideline 4.2 can mean changing the product itself, which at App369 starts with a paid consultation at $100 per 15 minutes, paid upfront. Approval stays Apple’s decision either way.

## Where to go next

- [Web app to the App Store: the route and what Apple checks](https://app369.com/fix/lovable-bolt-web-app-to-app-store/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review)
- [Can I publish my Lovable, Replit or Base44 app to the App Store?](https://app369.com/fixed-price/app-store-rejection-fix/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review#publish-ai-built-app)
- [Guideline 4.2 Minimum Functionality: the fix](https://app369.com/fix/app-store-guideline-4-2-minimum-functionality/?utm_source=simondziak&utm_medium=essay&utm_campaign=ai-built-app-app-store-review)

[All writing](https://simondziak.com/writing)

## Related

- [Home](https://simondziak.com/)
- [llms.txt](https://simondziak.com/llms.txt)
