Submitting multiple apps with only cosmetic differences, or an app that duplicates functionality already common on the Store without adding real value, falls under this guideline.
Why apps actually get flagged
Most commonly triggered by template-generated apps (the same shell with a different logo/color), or by resubmitting a rejected app under a new bundle ID instead of fixing the underlying issue.
A real example
"Your app duplicates the content and functionality of other apps submitted to the App Store, which is considered a form of spam."
The short version, in more detail
Guideline 4.3 is how App Review pushes back on apps that look like copies of something that already exists on the Store, whether that is another developer's app or your own. It is one of the most common rejections for small studios, template buyers and anyone who ships several similar apps. The reviewer is not judging code quality. They are asking whether this binary adds something distinct that a user could not already get elsewhere.
What this guideline covers
Design spam: apps that share the same structure, screens and flow as other apps, particularly several from one developer.
Saturated categories, where the Store already has many near-identical apps and a new one would add little.
Template and white-label apps that are repackaged with minimal changes.
Listings built to look like or borrow from a popular app's name, keywords or branding.
What usually triggers this rejection
Several apps from one account that share the same structure, screens and flow and differ only by name, icon or a swapped data set.
An app built from a purchased template or a white-label kit with only light re-skinning.
A crowded category (wallpapers, simple calculators, basic quiz or trivia apps, generic fitness trackers) where the app offers nothing obviously different.
Metadata that targets popular keywords or brand names so that the listing mimics a bigger app.
An app that is essentially one screen wrapped around a feature the system already provides.
How reviewers evaluate it
Reviewers compare the build against what is already on the Store and against other apps on the same developer account.
They look at features, flow and content, not source code or the quality of the engineering.
The decision is partly subjective, which is why two similar apps can get different outcomes.
Repeated 4.3 findings on one account are treated as a pattern, not as isolated mistakes.
Common misunderstandings
It is not about code. Clean, well-built code does not change whether the app is distinct.
A new name or icon does not make an app a different product in a reviewer's eyes.
It does not only apply to copying other people. Apps that duplicate your own earlier apps are covered too.
Common questions
Is 4.3 the same as copying someone else's app?
Not exactly. Copying is covered by a different guideline. 4.3 is about spam and duplication, including between your own apps.
Does this only affect small developers?
No, but small studios and template users see it most often because their apps are more likely to resemble others.
Can it affect my whole account?
Repeated violations can raise concern about the account as a whole, which is why many developers take a single 4.3 seriously.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.
Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.