Guideline 4.3: Spam

Guideline 4.3(a) - Design - Spam

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

Submitting similar or repackaged apps is a form of spam that creates
clutter and makes it difficult for users to discover new apps.

What it actually means

Apple believes your app is too similar to apps that already exist on the App Store. Not "inspired by" similar, but interchangeable similar: same layout, same features, same kind of content, with only the name and colours changed.

This is not about code quality. Your app can work perfectly and still be rejected under 4.3. The reviewer is answering one question: if this app disappeared, would anyone notice, or would one of the hundred apps like it do the same job?

It's worth knowing that 4.3 is the guideline Apple created specifically to fight template mills: companies that pump out hundreds of near-identical apps. That's the pattern your app got matched against, even if you only made one.

One guideline, though, is actually three different rejections, and they have different fixes:

• 4.3(b), saturated category. Your app competes in a niche flooded with lookalikes: face scan, tarot and astrology, calorie counting, wallpapers, VPNs, QR scanners, "AI [anything] generator" wrappers. The bar for standing out is higher because the reviewer has seen fifty of these this month.
• 4.3(a), similar to other developers' apps. Apple thinks your app duplicates a stranger's. Common for template and AI-built apps that converge on the same layouts.
• 4.3(a), similar to your own apps. If you publish several apps built the same way, the shared code, fonts, and packages can make Apple read them as one app resubmitted, even when the actual content differs.

The sixty-second test

Here's the detail that reframes this rejection: reviewers often spend less than a minute in an app. One developer's server logs showed the entire review session lasted under sixty seconds, with nothing typed into the app at all. If your app's distinctive feature only appears after the user enters something, the reviewer never saw it.

So the question is not "is my app meaningfully different?" It's:

Is the difference visible in the first sixty seconds, before anyone types anything?

That splits 4.3 rejections into two very different problems:

• Different but invisible: your app genuinely does something others don't, but it's buried behind input or onboarding. This is a presentation problem: front-load the distinctive feature, put it in the first screenshots, and write review notes that walk the reviewer straight to it ("Enter any question on the home screen, then tap Draw. The reading is generated live from your input").
• Genuinely generic: the app really is interchangeable with the top results. This is a product problem, and no amount of presentation saves it. Narrow the audience or add a capability the others don't have.

A real case from our own apps: a face-scanning app was rejected under 4.3. Adding features for a specific audience, cycle tracking for women, made it substantively different from generic face scan apps, and it passed. Audience narrowing is a real differentiation strategy, not a workaround.

Why AI-built apps hit this

AI app builders work from patterns they've seen before, so their output converges on the same handful of layouts: the same onboarding carousel, the same tab bar, the same card list, the same settings screen. To a reviewer who sees dozens of submissions a day, two unrelated AI-built apps can look like they came from the same factory, because in a sense, they did.

It gets worse if you prompted your tool with "build me an app like X." You asked for a duplicate, you got a duplicate, and Apple's job is to catch duplicates.

How to fix it

1. Run the sixty-second test. Open your app as a stranger would. Does anything distinctive appear before you type or tap through onboarding? If not, decide which problem you have: different-but-invisible (presentation) or genuinely generic (product).
2. Find your app's overlap. Search the App Store for your app's main keyword. Install the top three results. Be honest about what your app does that they don't. If the answer is "nothing yet," that's the actual problem to fix; the rest is cosmetics.
3. If it's presentation: front-load the difference. Move the distinctive feature to the first screen, make the first screenshots show it, and write review notes that tell the reviewer exactly what to tap to see it. Thirty seconds of notes prevents this entire class of rejection, and almost nobody writes them.
4. If it's product: narrow the audience or add a capability. A niche the big apps ignore, a genuinely different way of entering data, an integration they don't offer. Tell your AI tool to build that, specifically. "Invoicing for wedding photographers" survives 4.3; "Easy Invoice Maker" doesn't.
5. Replace template visuals and metadata. Change the icon, accent colours, onboarding screens, and any wording that could describe ten other apps. Your icon should not look like the default output of the tool you used.

What to write in Resolution Center

Adapt this to what you actually changed; don't send it unmodified:

Hello,

Thank you for the feedback. Since the rejection we've made changes to
differentiate the app:

- [Named feature]: a capability we haven't found in similar apps
- Redesigned icon, onboarding, and visual identity
- Rewritten App Store metadata to accurately describe the app's specific
  audience: [audience]

The app is built for [specific niche/use case], which isn't served by the
apps in this category. We'd appreciate a second look.

Thank you,
[Your name]

How to avoid it next time

Decide what makes the app different before you prompt an AI tool to build it, and put that difference in the prompt. "An app like Calm" produces a 4.3 rejection; "a wind-down app for shift workers whose bedtime changes every week" produces an app with a reason to exist. Differentiation is a product decision, and no tool makes it for you.

Related guides: 4.2: Minimum functionality (Apple thinks the app does too little, rather than duplicating others) and 2.3.7: Name, subtitle & keyword abuse (metadata that copies other apps' names).