Guideline 4.3 Design – Spam: why Apple rejected your app and how to fix it

What the rejection says

The message in Resolution Center usually reads something like this:

Guideline 4.3(a) – Design – Spam

We noticed your app shares a similar binary, metadata, and/or concept as apps previously submitted to the App Store, with only minor differences.

or, for the category version:

Guideline 4.3(b) – Design – Spam

Your app duplicates the content and functionality of other apps submitted to the App Store, which is considered a form of spam.

Apple’s wording varies, but it’s always one of those two ideas.

What Apple actually means

The guideline has two parts, and the fix depends on which one you got.

4.3(a): your own duplicates. Apple’s text: “Don’t create multiple Bundle IDs of the same app (for example, submitting a separate map app for every city in the world instead of a single worldwide map that allows users to search any city).” If you have one app per location, team, school or client, Apple wants a single app with the variations inside it, and suggests in-app purchase for paid variants.

4.3(b): the saturated-category rule. Apple’s text: “Don’t submit apps that are indistinguishable from what’s already widely available.” It names categories that are already crowded (dating, flashlight, sound effects, wallpaper, simple timers and fortune telling) and says new ones won’t be accepted “unless they offer a meaningfully different or improved experience.” It also calls drinking-game, Kama Sutra, fart and burp apps low-effort, and warns that repeated submissions “may lead to removal from the Apple Developer Program.”

Why AI-built apps hit it so often

• Same scaffold, same look. Rork, Bolt, FlutterFlow and Lovable templates produce recognisable layouts: the same tab bars, cards, onboarding carousels and default copy. To a reviewer who has seen hundreds of them, yours can look like one more.
• Crowded first ideas. The apps people prompt first are habit trackers, AI chat wrappers, wallpaper generators, timers, quote apps and dating ideas. Several of those are on Apple’s named list.
• Resubmitting under a new bundle ID after a rejection. That turns a 4.3(b) into a 4.3(a) and makes things worse.
• One app per client. Agencies and freelancers using AI to spin up near-identical apps for multiple businesses trip 4.3(a).

How to fix 4.3(a)

1. List every app in your account that shares code or concept with the rejected one.
2. Merge them into one app. Variations become settings, a location picker, or in-app purchases.
3. Remove or stop submitting the duplicates. Keep the bundle ID with the most history.
4. For white-label client work, each client should publish from their own Apple Developer account, under their own name. That’s the structure Apple expects for this.

How to fix 4.3(b)

Cosmetic changes don’t work here. You need a real difference in what the app does, and you need to show the reviewer where it is.

1. Name the one thing only your app does. A specific workflow, data source, audience or capability. If you can’t name it, the reviewer can’t either.
2. Put that thing on the first screen. Reviewers spend minutes, not hours. Put the differentiator in front of them, not three taps deep.
3. Replace template defaults: stock onboarding, placeholder copy, default icons, the generic tab bar. It’s the easiest signal of low effort to remove.
4. Rewrite the listing so the name, subtitle, screenshots and description describe that difference (see 2.3 Accurate Metadata).
5. Explain it in the review notes before you resubmit (below).

What to write back to App Review

Reply in Resolution Center before, or together with, your resubmission. Be specific and short:

Hello App Review,

Thank you for the feedback. We have made the following changes so the app
offers a meaningfully different experience:

1. [Specific capability] — [where to find it, e.g. "Home tab, first card"].
2. [Second capability] — [where to find it].
3. Removed template onboarding and placeholder content.

Unlike [category] apps, [App Name] [one sentence on what it does that
others don't]. A 40-second screen recording is attached.

Demo account: [email] / [password]

When to appeal instead

If your app really is different and the reviewer missed it, you can file an appeal with the App Review Board from the rejection in App Store Connect. Appeals work best when the reply above is already on record and the difference is obvious from a recording. Don’t appeal a template app. Fix it first.

How we handle a 4.3

We look at the rejected build next to the category it’s being compared with, find what makes it different (or build it if nothing does yet), put that on the first screen, rewrite the listing and review notes, and resubmit. If the app needs real product changes to pass, we quote that separately before we start.

Questions

Last reviewed 2026-09-23. Guideline quotes are from Apple’s App Review Guidelines; Apple can change them at any time.