Guideline 4.3 has two clauses, and neither one mentions a builder.
App Store Review Guideline 4.3 is titled Spam and it has exactly two clauses. 4.3(a) is about shipping one app under several Bundle IDs. 4.3(b) is about submitting an app nobody could tell apart from the apps the store already carries in quantity. That is the whole of it. There is no 4.3(c). Neither clause says anything about templates, code generators or AI, and the way to know that is to search the text, which we did on 21 October 2026 against the guidelines page that carries its own last updated date of 16 October 2026. The words template and app generation service appear in one place in the document, guideline 4.2.6, in a different section with a different test. If you came here from the broader question of app store rejection rates, the short answer carries over: Apple publishes no share for 4.3 either.
What follows is what each clause asks for, how to tell which one your rejection cites, what Apple's own help says about repeated similar apps, and what can happen to an app that is already live. One habit is worth more than the rest of this page: read the guideline number in your own rejection message before you read anybody's advice about it.
Start hereThe short version
One clause is about your catalogue. The other is about the store's shelf.
4.3(a) counts your own apps. If the same app exists several times under several Bundle IDs, that is the clause, and the fix Apple offers inside the clause is to ship one app and sell the variations as in-app purchases. The worked example in Apple's own text is a map app per city against one worldwide map with search.
4.3(b) counts everybody else's apps. It asks whether yours can be told apart from what is already widely available, and it names the categories where the bar is now high: dating, flashlight, sound effects, wallpaper, simple timers and fortune telling. In those, Apple says it will not accept a new submission without a meaningfully different or improved experience. The clause goes further on a second group, naming drinking games, Kama Sutra, fart and burp apps as low effort, and warns that repeated submissions of that kind can cost you your place in the Apple Developer Program.
What does guideline 4.3 actually say?
It sits in section 4, Design, between 4.2 Minimum Functionality and 4.4 Extensions. The heading is one word, Spam. Under it are two lettered clauses and nothing else. Plenty of guidelines in the document run to five or six sub-clauses, and several have entries marked intentionally omitted where Apple has retired a rule. 4.3 has neither. Two clauses, no gaps, no (c).
4.3(a) is the portfolio clause. Do not create multiple Bundle IDs of the same app. Apple explains why in the same breath: the result is unnecessary apps, and they make it harder for people to find the app they actually want. The example in the clause is a developer submitting a separate map app for every city in the world rather than one worldwide map with a search box. Where the variations are real, for a location or a sports team or a university, Apple's answer is one app that offers them as in-app purchases.
4.3(b) is the shelf clause, and it is longer. Do not submit apps that cannot be distinguished from what is already widely available. Apple's reasoning is about discovery: opportunistic variants of popular apps and popular categories degrade App Store discovery and reduce quality for users and developers alike. Then it names names. Dating, flashlight, sound effects, wallpaper, simple timers and fortune telling are called well established, and a new submission in one of them needs a meaningfully different or improved experience to be accepted at all. The clause also reserves the right to remove apps in those categories later if they are not updated, not improved, or do not attract customers.
The last sentence of 4.3(b) is the one to take seriously. A second group of app types gets a blunter label: drinking games, Kama Sutra, fart and burp apps are described as mediocre, low quality or low effort, and as adding no value to the App Store. Repeated submissions of that kind, the clause says, may lead to removal from the Apple Developer Program. That is the account, not the app. Three other clauses in section 4 carry the same threat, for impersonation, for Safari extensions and for abusing Apple services, which puts 4.3(b) in the small group where a pattern of submissions is treated as conduct rather than as a product problem.
Apple, App Review Guidelines, last updated 16 October 2026, read 21 October 2026
Find the clause
Which guideline is yours, really?
Pick the sentence that describes your situation. Seven situations here, and only four of them are guideline 4.3.
Nothing picked yet. Your rejection message in App Store Connect names the guideline, so read the number there before you read anybody else's theory about it.
Read from the App Store Review Guidelines on 21 October 2026. The rejection message is still the only thing that tells you which clause App Review actually cited.
Is 4.3(a) a different problem from 4.3(b)?
They share a heading and almost nothing else. 4.3(a) can be answered with a release plan. You have six apps that are one app, so you keep one Bundle ID, move the differences behind a purchase or a setting, and the six listings become one. Nothing about the product has to change. Apple tells you to do exactly this on its own App Review page, in an entry headed Repeated submission of similar apps: submitting several apps that are essentially the same ties up review and risks none of them passing, and the advice is to combine them into one.
4.3(b) cannot be answered with a release plan at all. The clause compares your app against a shelf you do not control, and the standard it sets is a meaningfully different or improved experience. Merging Bundle IDs does not move that. Renaming does not move it. The only thing that moves it is the app doing something the established ones do not, and being able to say what that is in a sentence. If you cannot write that sentence, a reviewer is unlikely to find it for you.
This is why the clause letter in your rejection message matters more than the guideline number. Both arrive as 4.3 in conversation, and the work they ask for is weeks apart. Read the message in App Store Connect and note which letter App Review cited, because that is the only authoritative statement of what they looked at.
It also helps to know which of your problems are judgement calls and which are not. A rejection like an app icon alpha channel rejection turns on a property of a file, so you can check it yourself before you upload and the answer is the same every time. 4.3 is the other kind. Two reviewers could read the same app differently, which is why the clause text and the named categories are worth knowing before you build rather than after you submit.
Does Apple name generated apps as a 4.3 trigger?
No. We read the whole guidelines document on 21 October 2026 and searched it. The word template occurs twice and the phrase app generation service occurs once. All three are in guideline 4.2.6. Elsewhere in the document the word generated belongs to user generated content, which is guideline 1.2 and about moderation. 4.3 contains none of them. So the widely repeated line that 4.3 is the spam guideline that catches AI built apps is an inference, and the documentation does not support it.
The guideline that does name generation services is 4.2.6, and its test is about authorship of the submission rather than authorship of the code. Apps created from a commercialized template or an app generation service are rejected unless they are submitted directly by the provider of the app's content. The clause then tells those services what to do instead: give clients tools to create customized apps of their own, or host all client content inside a single binary on a picker model, which it illustrates with a restaurant finder holding a separate page per client restaurant. If you own the content and you submit from your own account, 4.2.6 is satisfied and nothing in it concerns how the code was written.
One more absence is worth naming, because it is checkable. App Review Help has a section called guideline reference, and as of 21 October 2026 it holds four pages: 2.3.3 on screenshots, 4.1 on copycat and impersonation rejections, 5.1.1(ii) on purpose strings and 5.1.1(v) on account deletion. There is no page for 4.3 and none for 4.2.6. Apple wrote the explainer for copycats and has not written one for spam. Everything authoritative about 4.3 is the two clauses themselves.
None of that makes a generated app safe from 4.3(b), because that clause looks at the finished app. A flashlight is a flashlight whoever typed it. The thing to take from the reading is narrower and more useful: the clause you need to satisfy for code you did not type by hand is 4.2.6, about who submits, and the clause you need to satisfy for the idea is 4.3(b), about whether the shelf already has it. Thin apps also run into a third one, which the minimum functionality rejection guide takes apart on its own.
Apple, App Review Guidelines, guideline 4.2.6, read 21 October 2026
What happens after a 4.3 rejection, and can a live app be removed?
The rejection itself arrives in App Store Connect with the guidelines your submission did not follow named in it, and you can reply to App Review in the same place before you upload a new build. Apple's App Review page, read 21 October 2026, is explicit that this correspondence is the first step rather than a formality. For what the queue costs you while you work, the same page says App Review typically reviews at least half of submissions in under 24 hours and 90 percent in under 48 hours.
If you believe the review misread the app, there is a route past the reviewer. Apple asks for one appeal per submission that did not pass, with specific reasons why you think the app complies, and only after you have answered any requests for more information. A 4.3(b) appeal lives or dies on the sentence that says what your app does that the established ones do not, so write that first. The appeal app store rejection walkthrough covers the form and the wording.
An approval is not the end of 4.3 either, and the clause says so itself. Apple reserves the right to remove apps in the established categories later if they are not updated, improved, or do not attract customers. Two App Review Help pages put numbers on that, both read on 21 October 2026. Respond to an app removal says apps with less severe issues may be given 14 days to fix them before the app comes down, apps with serious issues such as safety or legal concerns may be removed immediately, and apps whose concept is fundamentally incompatible come down and cannot be restored at all. App Store Improvements covers the stale half: an app that has not been updated in three years and also fails a minimal download threshold over a rolling 12 month period gets a notice in App Store Connect and 90 days to submit an update. An app that crashes on launch is removed immediately.
Two answers on that App Store Improvements page are easy to miss and both work in your favour. A removed app keeps its name, which stays attached to your account rather than freeing up for somebody else. And people who already installed it keep a working app, in-app purchases included. What you lose is the listing and every new download, which for most apps is the whole business. The page also sets no deadline for coming back: submit an approved update whenever you like, as long as your Apple Developer Program membership is still active.
Apple, App Review, review status and appeals, read 21 October 2026
The guidelines people file under 4.3
| The clause | What the text is about | The fix Apple names | Has its own help page |
|---|---|---|---|
| 4.3(a) Spam | Several Bundle IDs of one app | One app, variations through in-app purchase | No |
| 4.3(b) Spam | An app the store already carries in quantity | A meaningfully different or improved experience | No |
| 4.2 Minimum Functionality | Not enough beyond a repackaged website | Features, content and interface of its own | No |
| 4.2.6 | Who submits a template or generated app | The provider of the content submits it | No |
| 4.1 Copycats | Copying another app's name, interface or brand | Your own idea and your own metadata | Yes |
Help page column from the guideline reference section of App Review Help, which lists four pages as of 21 October 2026 and none of them for 4.3.
Where this lands if a builder wrote your app
Two clauses apply and they apply in a fixed order. 4.2.6 asks who submits, and the answer has to be you, from your own developer account, because you own the content. 4.3(b) then asks what the app is, and that answer has to come from you. The honest version is that a builder removes the typing and leaves the harder half of the review on your desk.
Newly is an AI app builder. You describe an app in plain English and it writes a real React Native and Expo project you own, with two way GitHub sync so the code is yours to read and change. It uploads iOS builds to TestFlight, publishes to Google Play internal testing and can build a standalone Android APK. Paid plans start at $25 a month and there is no free tier. It does not submit to the App Store for you, which is 4.2.6 as intended: Apple wants the content owner to submit, so you do.
For 4.3 the useful practice is to decide your answer before you build. Open the App Store, search your category, and read the first ten results properly. If your idea is already there six times, you have found 4.3(b) early and cheaply, and you can change the idea while changing it costs nothing. If what you are building is one app for one business, with your own data and your own workflow in it, neither clause is aimed at you and a reviewer will see that in the first minute.
Questions people ask about guideline 4.3 spam rejections
It is titled Spam and it has two clauses. 4.3(a) tells you not to create multiple Bundle IDs of the same app, and the example in the clause is a separate map app for every city instead of one worldwide map that lets people search any city. Apple's suggested fix is a single app with the variations offered through in-app purchase. 4.3(b) tells you not to submit apps that are indistinguishable from what is already widely available. It names dating, flashlight, sound effects, wallpaper, simple timers and fortune telling as categories where Apple will not accept new submissions unless the app offers a meaningfully different or improved experience. It names drinking games, Kama Sutra, fart and burp apps as low effort and says repeated submissions of that kind may lead to removal from the Apple Developer Program. Read on the App Review Guidelines page on 21 October 2026, which carries its own last updated date of 16 October 2026.
Build the app the shelf does not already have
Before you write a line, look at what your category already carries and name the part of your app that is in none of it. That answer is the one 4.3(b) asks for, and no tool can supply it.
Start building