Guideline 4.3 is Apple's spam rule. It is commonly applied when an app appears to duplicate an existing product, repeats a template, or adds another near-identical listing to an already crowded category. A new icon or a rewritten subtitle rarely addresses the reason for the rejection.
Know which part of 4.3 applies
Section 4.3(a) focuses on multiple Bundle IDs for substantially the same app, including portfolios split by location, client, or theme. Section 4.3(b) covers apps that are indistinguishable from products already common in a saturated category. The first asks whether the variants should be one product. The second asks whether the product itself adds a meaningful experience.
Start with the reviewer note
Read the exact note in App Store Connect and separate the evidence from the conclusion. Write down what the reviewer called similar: the product concept, the binary, the listing, the account portfolio, or the category itself. Do not resubmit until you can explain the distinction in one sentence.
If the screenshots, first-run flow, and core outcome look interchangeable with another app, the reviewer probably will not see a distinct product either.
Check the product, not only the listing
- Core outcome: identify the job your app performs that the compared apps do not.
- Experience: show where the workflow, audience, content, or data is materially different.
- Ownership: collect licenses and authorization for branded content, templates, or third-party assets.
- Portfolio: explain why this needs to be a separate app instead of a mode inside an existing one.
Prepare a clean review note
Keep the response factual. Name the differentiating workflow, point the reviewer to it, and include any credentials needed to reach it. If the previous build caused confusion, state what changed in the new build. Avoid arguing that competitors were approved; review is based on the submitted app.
What is distinct:
[one clear product difference]
Where to find it:
[screen and exact steps]
What changed in this build:
[material product changes]
Supporting rights or context:
[licenses, ownership, account relationship]Changes that usually do not solve 4.3
A new icon, color palette, app name, or screenshot order can make the listing look different while leaving the product unchanged. Removing a reference to a template does not remove shared code or an interchangeable workflow. If the reviewer cannot reach the distinct value within the supplied account and steps, assume it is not yet demonstrated.
Resubmit or appeal?
Resubmit when you changed the product or can now demonstrate a difference the reviewer could not access. Appeal when the submission already complies and the rejection appears to rely on a factual misunderstanding. In either case, send one coherent record instead of several fragmented messages.
Before you press submit
- The reviewed build contains the promised changes.
- Screenshots and metadata describe the current product.
- The differentiating workflow is reachable with the supplied review account.
- Your note is specific, short, and free of comparisons you cannot prove.
Was this article helpful?