# Guideline 4.1 Copycats: App Rejected as a Copy, What Now?

> Guideline 4.1: Apple rejects apps that imitate another app's name, icon or interface. Keep the problem you solve, invent everything that identifies your app.

Original page: [Guideline 4.1 Copycats: App Rejected as a Copy, What Now?](https://devoria.fr/en/blog/guideline-4-1-copycats-app-rejected)
Author: [Mehdi Azizi](https://devoria.fr/en/mehdi-azizi)
Published: 2026-11-04
Content last revised: 2026-11-04


Guideline 4.1, "Copycats," rejects an app that passes itself off as another one: same name, same icon, same interface, or a listing that rides on a well-known app's fame. **You can solve a problem other apps already solve, but you can't take over one of their identities.** Since November 2025, 4.1(c) also forbids putting another developer's name, brand or icon in your name or icon without their permission.

I publish my own iOS apps: Solys, TradaZen and Nolera are on the App Store. This guide is based on Apple's official text, read on October 15, 2026, its help page dedicated to 4.1, and rejections published by developers. The apps mentioned as copies are fictional examples. If your rejection talks about similar apps or a saturated category, read the [guideline 4.3 Spam](https://devoria.fr/en/blog/guideline-4-3-design-spam-app-rejected) guide instead.

## What does guideline 4.1 say?

4.1 opens the "Design" section of the [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/#4.1). It's split into three parts: (a), (b) and (c).

| Part   | What it forbids                 | Rejection example        |
| ------ | ------------------------------- | ------------------------ |
| 4.1(a) | Copying a popular app           | Clone of a hit game      |
| 4.1(b) | Impersonating an app or service | Fake banking app         |
| 4.1(c) | Someone else's name or icon     | Famous brand in the name |

(a) starts with "Come up with your own ideas." Apple refuses apps that copy "the latest popular app," or that tweak another app's name or interface slightly and pass it off as their own. Apple also reminds you that copying exposes you to an intellectual property infringement claim.

(b) targets impersonation: publishing an app that pretends to be another app or a service. Apple treats it as a violation of its Developer Code of Conduct, which can get you removed from the program.

(c) is the newest. Apple added it on [November 13, 2025](https://developer.apple.com/news/?id=ey6d8onl): "You cannot use another developer's icon, brand, or product name in your app's icon or name." In other words, no other developer's icon, brand or product name in your name or icon, unless they agree.

[Apple's help page on 4.1](https://developer.apple.com/help/app-review/guideline-reference/4-1-prevent-copycat-rejection) goes further than the text. It advises against popular app names and trademarks in every field of your listing. It also asks for accurate developer information, including your name and support URL, to make impersonation harder.

## The 4.1 rejection message and what it means

The message opens with "Guideline 4.1 - Design - Copycats," sometimes followed by the part letter. On Apple's forums, three families keep coming up.

**Your app imitates a well-known app.** The typical message starts with "This app or its metadata appears to be misrepresenting itself as another popular app or game." This text, [published by a developer](https://developer.apple.com/forums/thread/750840), targets the app or its listing. The imitated app can come from the App Store or another platform. Often, the message doesn't name it.

**Your app uses third-party content.** Another rejection [posted on the forums](https://developer.apple.com/forums/thread/756718) mentions "potentially misleading references to third-party content": in this case, sports teams and leagues without authorization. Apple offers two ways out. Attach proof of your rights in App Store Connect, or remove that content from the app and the listing.

**The name comes from your own app.** In August 2026, a developer [described repeated 4.1(a) rejections](https://developer.apple.com/forums/thread/842458) for the title of his own game, already published on Google Play. In that case, it's on you to prove the name belongs to you.

> The 4.1 message targets the app or its listing. Changing the app without rereading the name, subtitle, keywords and screenshots isn't always enough.

## 4.1, 4.3 or 5.2: three different questions

These rules overlap but don't ask the same question.

| Rule           | Question asked                   | What you fix                   |
| -------------- | -------------------------------- | ------------------------------ |
| 4.1 Copycats   | Does it imitate another app?     | Name, icon, interface, listing |
| 4.3 Spam       | Is it just one more app?         | The concept and the code       |
| 5.2 IP         | Do you have the rights?          | License or removal             |
| 2.3.7 Metadata | Does the listing exploit a name? | Name, subtitle, keywords       |

[Rule 5.2.1](https://developer.apple.com/app-store/review/guidelines/#5.2.1) forbids using other people's trademarks, works or patented inventions without permission, as well as "copycat" names or metadata. 5.2.5 adds a case: an app that could easily be mistaken for an Apple app, like Messages or the App Store. The rights you need to prove are detailed in the [guideline 5.2.1 guide](https://devoria.fr/en/blog/guideline-5-2-1-intellectual-property-app-rejected). On the listing side, [guideline 2.3.7](https://devoria.fr/en/blog/guideline-2-3-10-app-rejected-accurate-metadata) rejects popular app names slipped into metadata to grab searches.

4.3 judges something else: an app that shares its code, listing or concept with others. After removing the sports teams, the developer mentioned above got a 4.3(a) rejection the next day, in June 2024. Among the possible causes, the message mentioned buying a template from a third party "with problematic code."

**Fixing a 4.1 means changing what identifies the app. Fixing a 4.3 means changing what it does.**

## The "get inspired without copying" grid

Here's the grid I apply before building. It turns Apple's help page into concrete decisions. It's my reading, not an official list.

| Element           | You can                      | Gets you rejected               |
| ----------------- | ---------------------------- | ------------------------------- |
| Problem solved    | Same as a well-known app     | The app copied as is            |
| Name              | An invented name             | Famous name followed by "Pro"   |
| Icon              | Your shape, your colors      | Same pictogram, same hue        |
| Interface         | iOS conventions              | Screens copied identically      |
| Game mechanics    | A genre, with your twist     | Rules and grid of a hit         |
| Palette           | Your own colors              | A famous brand's colors         |
| Text and sounds   | Created for your app         | Taken from another app          |
| App Store listing | Your words, your screenshots | Competitor used as a keyword    |
| Third-party brand | With written permission      | Team logo without a license     |
| Developer name    | Your name or company         | Name close to a known publisher |

**If someone could mistake your app for another one on its listing or first screen, you're in 4.1 territory.** A tab bar or a list doesn't copy anyone: Apple asks you not to copy "the look and feel" of another app, not to reinvent every button.

## Template, kit or generated code: keep your own identity

A template, a starter kit or an AI-generated project gives you code and screens, not an identity. And Apple judges what the reviewer sees: name, icon, screens, text and listing.

The 4.1 risk comes from what you forget to change. The demo name, default icon, sample palette, placeholder text and the seller's screenshots end up in every app built from the same template. If the template itself imitates a famous app, you inherit the copy. Rule 4.2.6, detailed in the [guideline 4.2 guide](https://devoria.fr/en/blog/guideline-4-2-minimum-functionality-app-rejected), also rejects apps built from a commercial template, unless the content provider submits them directly.

Before submitting an app that started from a template, change at least:

1. **The display name and the listing name**, invented for your app.
2. **The icon**, designed for your app, not the sample icon recolored.
3. **The palette and illustrations**, even if you keep the screen structure.
4. **All the text**, from onboarding to error messages.
5. **The screenshots and description**, made from your actual app.

My recent apps share the same technical foundation, the one the iOS & Android Kit's Starter Code comes from. Yet Solys, TradaZen and Nolera share neither name, icon nor main feature: an alarm clock with mini-games, a trading simulator and a wardrobe app. For an AI-generated project, I explain the method in [build an iOS app with AI](https://devoria.fr/en/blog/build-ios-app-with-ai-pitfalls-checks).

## Responding to a 4.1 rejection

1. **Identify the family.** Imitating an app, third-party content, or a name that's already yours: the answer isn't the same.
2. **If the name or brand is yours, prove it.** Attach documents in the App Review Information section of App Store Connect: your other app's listing, identity of the account that publishes it, trademark filing if you have one.
3. **If you use someone else's brand, remove it everywhere.** Name, subtitle, keywords, icon, screenshots and app screens. Or get the owner's written permission, as 4.1(c) allows.
4. **If the interface looks too similar, change the screens.** Touching up the listing isn't enough when the app itself is what imitates.
5. **Ask which element is the problem.** Apple's page on how to [contact App Review](https://developer.apple.com/help/app-review/after-submitting-for-review/contact-app-review) recommends being specific about what you're asking.
6. **Appeal only if your app follows the rule.** The [App Review Board](https://developer.apple.com/help/app-review/after-submitting-for-review/appeal-to-the-app-review-board) accepts only one appeal per rejected app, after you reply to the rejection message.

Here's the reply template I'd use, to adapt:

```text
Hello App Review team,

Thank you for your feedback regarding Guideline 4.1.

[App name] is an original app. We reviewed every element
that could resemble another app:
- Name and icon: created for this app, no third-party brand.
- Interface: [what is specific to our screens].
- Metadata: no other app names or trademarks in any field.

[Only if true] "[Name]" is also the name of our app on
[platform], published by the same developer. Proof is
attached in App Review Information.

Could you tell us which app or element looks similar,
so we can address it precisely?

Best regards,
[Your name]
```

Only write what's true. A false claim in a reply to Apple makes your case worse.

## The 4.1 checklist before submitting

- Your name and icon don't resemble any well-known app.
- No one else's brand in the name, subtitle, keywords or screenshots.
- Every third-party brand shown has written permission, or it's gone.
- No screen is copied from another app.
- Text, sounds and illustrations were created or bought for your app.
- Every sample element from the template is gone.
- Your developer name and support URL are accurate.

To pick the words for your listing without naming a competitor, the method is in [App Store ASO for beginners](https://devoria.fr/en/blog/app-store-keywords-how-to-choose).

## Your own identity from your next submission

If your app was just rejected under 4.1, the [Review Kit](https://devoria.fr/en/kits/app-review) helps you find the cited rule and what it requires, with note templates for the reviewer. If you're starting from a Starter Code, the [iOS & Android Kit](https://devoria.fr/en/kits/ios) path begins with the idea, the audience and the price, then puts the code in your name. For a human look, [book an hour with me](https://devoria.fr/en/coaching). The full approach is on the [app rejected by Apple](https://devoria.fr/en/expertise/app-rejected-by-apple) page, and the other reasons in [why Apple rejects an app](https://devoria.fr/en/blog/apple-app-rejection-real-cases).

If you're preparing your first release, [take your free diagnostic](https://devoria.fr/en/diagnostic): it puts the steps in order and sends you my Apple anti-rejection checklist. The homepage shows how to [build a mobile app](https://devoria.fr/en) with review in mind from day one.

## Frequently asked questions

### What does "Guideline 4.1(a) - Design - Copycats" mean?

It's the copy rejection. Apple thinks your app, or its listing, is passing itself off as a popular app or game, on the App Store or elsewhere. Often the message doesn't name the app in question: reread the name, icon, interface and every field of the listing.

### Can you take inspiration from an existing app?

Yes, from the problem it solves and from iOS conventions. No, from its identity: name, icon, screens, text. Apple's help page even encourages "a unique spin on an existing concept," meaning your own take on an existing concept.

### Can you mention another app in your listing or keywords?

No. The 4.1 help page advises against popular app names and trademarks in every field of the listing, and 2.3.7 rejects them in metadata.

### What's the difference between guideline 4.1 and 4.3?

4.1 checks whether your app imitates a specific app. 4.3 checks whether it's just one more app: same code or concept as others, or a saturated category. The same app can get both, one after the other.

### My app has the same name as my Android app: what should I do?

Attach proof that both apps are yours in the App Review Information section of App Store Connect, then reply to the message. If the rejection comes back despite clear proof, an appeal to the App Review Board is justified.


## Your project

[Review Kit](https://devoria.fr/en/kits/app-review): My App Store review checklist, the Apple rejections I fixed, a Google Play checklist and three Claude Code skills. $55.

[iOS & Android Kit](https://devoria.fr/en/kits/ios): Build your iPhone and Android app with Claude Code: the starter code from my apps, the path all the way to the stores, and every kit. $109.

[Diagnostic: what's between you and your iPhone app](https://devoria.fr/en/diagnostic): 7 questions, 60 seconds: find out what's really stopping you from publishing your iPhone app, get your 4-step path and the kit that fits you.