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

This guide quotes the App Review Guidelines as last updated by Apple on October 16, 2026, Apple's App Review help pages, and rejection messages and App Review replies that developers posted on Apple's Developer Forums. Apple doesn't publish how it detects spam, so where this post describes what helped other developers, it says so.

#What Guideline 4.3 says

Guideline 4.3 sits in the Design section of the App Review Guidelines, which is why the rejection is titled "Design – Spam". It has two parts.

4.3(a): the same app more than once. Apple's example is a separate map app for every city instead of one worldwide map. The guideline says not to create multiple Bundle IDs of the same app, and suggests that versions for different locations, sports teams or universities be offered inside a single app, for example with in-app purchase.

4.3(b): an app that adds nothing new. The current text says: "Don't submit apps that are indistinguishable from what's already widely available." It names categories that are "well established on the App Store": dating, flashlight, sound effects, wallpaper, simple timers and fortune telling. Apple won't accept new apps in them "unless they offer a meaningfully different or improved experience", and may remove existing ones that aren't updated, improved or don't attract customers. A second list (drinking games, Kama Sutra, fart and burp apps) is called low-effort, and repeated submissions of those can lead to removal from the Apple Developer Program.

Apple rewrote both parts on June 8, 2026 to "clarify the basis for the guideline" and add the examples above. If you read an older blog post that talks about "piling on to a saturated category", that's the previous wording. The idea is the same, but today's text also covers removing existing apps.

Guideline 4.3 is not the same as 4.1 Copycats. 4.1 is about copying a specific app's name, icon, brand or UI, or impersonating another service. 4.3 is about being one more near-identical app, even if you copied nobody in particular.

#Read your rejection message carefully

The guideline number tells you which rule; the first sentence tells you what App Review compared your app with. Developers have posted several versions on the Developer Forums:

The 4.3(a) message usually ends with a "Resources" list of factors that can lead to a spam rejection. In the versions developers have posted (example, example) the list is:

1. the same source code or assets as other apps already on the App Store,
2. several similar apps made from a repackaged app template,
3. an app template with problematic code bought from a third party,
4. several similar apps submitted across multiple accounts.

Most messages don't name the app yours resembles. Developers ask, and the usual answer from App Review on the forums is the same general sentence: such apps "share a similar binary, metadata, and overall concept as apps already on the App Store, with only minor differences" (example reply). So you have to work out the overlap yourself.

#What App Review compares

Binary. The app you upload, with its code and bundled assets. Apple doesn't say how it compares binaries. What the rejection message names is reused source code, reused assets, repackaged templates and purchased templates. Note that App Review sees your app, not your repository: "similar binary" means the built app and what's inside it.

Metadata. Your App Store product page: name, subtitle, description, keywords, screenshots and icon. A description adapted from another app, stock screenshots or a template's sample content all make an app look like the others.

Concept. What the app does and for whom. This is what 4.3(b) is about, and it's the one you can't fix with a new build. A daily horoscope app with a fresh codebase is still a daily horoscope app.

#How to avoid a 4.3 rejection before you submit

Ship one app, not variants. If you're thinking about separate apps for each city, language, team, client or theme, make one app and let people choose inside it. That's Apple's own suggestion in 4.3(a), and the message for content-only variants says the same.

Be careful with templates, purchased code and app builders. Three of the four factors in Apple's rejection message are about reused or bought code and repackaged templates. If you start from a template, you're starting from something other developers may already have shipped. Replace the sample content, images, sounds and icons, and build the parts that make your app what it is yourself. Guideline 4.2.6 adds that apps made from a commercial template or app generation service are rejected unless the provider of the app's content submits them.

Know if you're in a crowded category. If your app is in one of the categories 4.3(b) lists, assume App Review will ask what's different. In 2026 an astrology app with a "Tarot card of the day" feature was rejected, and the App Review Board upheld the rejection, as Daring Fireball's correction of its earlier story describes. Fortune telling is one of the categories 4.3(b) names. The list isn't exhaustive either: a developer on the forums reports a party game for getting to know each other being rejected under 4.3(b) as a saturated category.

Make the difference visible in the app. App Review reviews what it can see. If your app's difference is a workflow, a data source or a design choice, it should be the first thing a reviewer meets, not something behind onboarding, a paywall or a settings screen. Provide a demo account if needed.

Make your product page your own. Write your own description, show your actual app in the screenshots (Guideline 2.3.3), and leave other apps' names out of your metadata (Guideline 4.1). A product page that reads like ten others makes your app look like ten others.

Explain it in the review notes. App Store Connect has a Notes field in App Review Information. Use two or three plain sentences: who the app is for, what it does that existing apps don't, and where in the app the reviewer can see it. Guideline 2.3.1(a) already asks you to describe new features with specificity there.

Keep one account and a clean history. "Several similar apps across multiple accounts" is one of the named causes, and a new account doesn't hide a matching binary. If you bought an app or its code, or a contractor built it, keep records of where the code came from. One developer resolved a repeat 4.3(a) rejection tied to a terminated account by showing documentation of their history and then talking to Apple on a call (thread).

#What to do after a 4.3 rejection

1. Work out which part you hit. Use the table above. 4.3(a) points at your build, your accounts or your other apps. 4.3(b) points at your concept.

2. Reply to the rejection in App Store Connect. Apple's appeal page asks you to do this before appealing. Explain concisely what your app does that existing apps don't, where to see it, and, if the message mentions code or templates, where your code comes from. Developers who replied with a list of genuinely distinct features have reported approvals afterwards. Developers who only changed colours and icons generally haven't.

3. Ask App Review directly if you don't understand the rejection. You can request a 30-minute App Review appointment through Meet with Apple, on Tuesdays and Thursdays during local business hours. It's informational: App Review can explain how the guideline applies but won't preapprove your app.

4. Change the app, or appeal, not both. If the rejection was right, change the concept or the build and resubmit. If you believe your app complies, appeal to the App Review Board. Apple's guidance: one appeal per rejected app, cite the guideline and explain point by point how your app meets it, and don't appeal if you've already changed the app and resubmitted. A complete appeal doesn't guarantee a different result.

If an update to a live app was rejected: the guidelines say bug fixes for apps already on the App Store won't be delayed over guideline violations, except legal or safety issues. Reply in App Store Connect and ask to use the Bug Fix Submission process, then deal with the 4.3 concern in the next version.

#What not to do

• Don't open a new developer account and submit the same app there. "Similar apps across multiple accounts" is one of the named causes, and Apple's guidelines warn that repeated spam can lead to removal from the Apple Developer Program.
• Don't resubmit the same build with a new name or new screenshots. The repeat message starts "We continue to notice…".
• Don't add one small feature and call it different. "Minor differences" is the exact problem the guideline describes.
• Don't argue that the category is big enough for one more app. For 4.3(b), that's the argument the guideline rejects.

#Choosing an idea that won't hit 4.3(b)

4.3(b) is easiest to avoid before you write code. A crowded category is a demand signal, but it's also where "meaningfully different" is hardest to prove. When you look at an app idea:

• List the five apps a reviewer would compare yours with, and write one sentence on what yours does that none of them do. If you can't, App Review won't find it either.
• Look at what users of those apps complain about. Complaints you can fix are a difference that also helps you sell.
• Prefer a specific audience over a general one. "A timer" is crowded; a timer built around a specific job, sport or condition is a different product.

Fledly shows the young apps already earning in an app concept, their prices and their users' complaints, so you can see what exists before you build. Our method for testing an idea is in how to validate an iOS app idea, and app ideas solo developers can't copy covers ideas that are hard to clone.

#Frequently asked questions

#What does "Guideline 4.3(a) - Design - Spam" mean?

App Review found your app too similar to other apps already submitted, in its binary (code and assets), its App Store metadata or its overall concept, with only minor differences. The other apps can be other developers' apps, apps from a terminated account, or your own apps. The rejection message usually lists reused code or assets, repackaged or purchased templates, and similar apps across several accounts as common causes.

#What is the difference between Guideline 4.3(a) and 4.3(b)?

4.3(a) is about duplicates: the same app under several Bundle IDs or accounts, or apps built from the same code, assets or template. 4.3(b) is about apps that are indistinguishable from what's widely available, especially in established categories such as dating, flashlight, sound effects, wallpaper, simple timers and fortune telling, where Apple only accepts apps that offer a meaningfully different or improved experience.

#Why did my original app get a Design Spam rejection?

Writing your own code doesn't rule out 4.3. App Review looks at the binary, the metadata and the concept together. A common engine or library, stock assets, a product page that reads like other apps, or a concept with many existing apps can each lead to a 4.3 rejection. Apple usually doesn't name the similar apps, so reply in App Store Connect explaining what your app does differently, or request an App Review appointment to ask.

#Will changing the design or icon fix a 4.3 rejection?

Usually not on its own. The guideline is about apps that differ only in minor ways, and developers on Apple's forums report rejections continuing after visual changes. Changes that address the cause help: replacing reused code or assets, merging variants into one app, or adding a genuinely different experience and explaining it in the review notes.

#Can I appeal a Guideline 4.3 rejection?

Yes. Reply to the rejection in App Store Connect first. If that doesn't resolve it, submit an appeal to the App Review Board, citing Guideline 4.3 and explaining point by point how your app meets it. Submit one appeal per rejected app, and don't appeal if you've already changed the app and resubmitted. An appeal doesn't guarantee a different outcome.

#Can a 4.3 rejection get my developer account terminated?

A single rejection doesn't terminate an account, but Apple's guidelines say repeated submissions of low-effort apps under 4.3(b) may lead to removal from the Apple Developer Program, and submitting similar apps across multiple accounts is one of the named causes of 4.3(a) rejections. Don't work around a rejection with a new account.

#Can I publish the same app for different cities, clients or languages?

Apple's guidance is one app with the variations inside it, for example selectable content or in-app purchases, rather than separate apps with separate Bundle IDs. Separate apps that only differ in content or language are a common cause of 4.3(a) rejections.

#Sources

• Apple, App Review Guidelines, sections 2.3.1, 2.3.3, 4.1, 4.2.6, 4.3 and 5.6, and "Bug Fix Submissions" (last updated October 16, 2026; checked October 30, 2026).
• Apple Developer News, Updated Apple Developer Program License Agreement and App Review Guidelines now available, June 8, 2026 (4.3(a) and 4.3(b) revised).
• Apple App Review help: Appeal to the App Review Board, Request a one-on-one App Review appointment, 4.1 Preventing copycat and impersonation rejections, App Store Improvements.
• Rejection messages and App Review replies posted on the Apple Developer Forums, 2017–2026: threads 84738, 757046, 769509, 773355, 799394, 812849, 815956, 825522. These are individual developers' accounts.
• John Gruber, Retraction: The App Store Rejection of the Week That Was, in Fact, a Correct Rejection, Daring Fireball, August 2026.