What the rejection typically looks like
Guideline 4.1 - Design - Copycats
This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform.
Apps should be unique and should not attempt to deceive users into thinking they are downloading something they are not.
Specifically, the app resembles [another popular app].
Next Steps
Learn more about requirements to prevent apps from impersonating other apps or services in guideline 4.1. Revise the app to comply with these requirements. Once the app is fully compliant, resubmit the app for review.
Paraphrased example – the exact wording in your message may differ.
What Guideline 4.1 Copycats actually says
Guideline 4.1 sits in the Design section of the App Store Review Guidelines and currently has three parts:
- 4.1(a) – Original ideas. Apple asks you not to "simply copy the latest popular app on the App Store", or to make minor changes to another app's name or UI and pass it off as your own.
- 4.1(b) – Impersonation. Submitting apps that impersonate other apps or services is treated as a violation of the Developer Code of Conduct and "may result in removal from the Apple Developer Program." That puts your account at risk, not just one submission.
- 4.1(c) – Icons and names. You cannot use another developer's icon, brand or product name in your app's icon or name without that developer's approval. This part was added in Apple's November 2025 guideline update.
The core concept is misrepresentation. The standard rejection text says your app or its metadata "appears to be misrepresenting itself" as another popular app or game – and that app does not have to be on the App Store. It can come from a developer's website, another distribution source or a third-party platform such as a web game or an Android app. Reviewers judge from the user's perspective: could someone seeing your icon, name and screenshots in search results believe they are getting the other product?
If the reviewer focuses on trademarks or copyrighted assets you have no license for, you may see Guideline 5.2.1 Intellectual Property cited alongside or instead of 4.1. A 5.2.1 issue can often be resolved by removing the material or providing permission documents; a 4.1 issue usually needs visible differentiation unless you are the rights holder. If the app you resemble is an Apple product or interface, Guideline 5.2.5 (Apple Products) can apply as well.
Common reasons apps get rejected under 4.1
- Brand names in your app name. Names like "Downloader for [Social Network]", "[Messenger] Status Saver" or "[Game] Guide" can trigger 4.1(c) directly. Calling the app "unofficial" doesn't make the name acceptable. Downloader apps can also run into Guideline 5.2.3 (Audio/Video Downloading).
- A look-alike icon. The same glyph, color combination or silhouette as a well-known app reads as impersonation at icon size, even if your designer redrew it.
- Cloned UI. In one case discussed on the Apple Developer Forums, a word game removed every reference to a famous word puzzle from its metadata and was rejected again because its UI still closely resembled the original game.
- Viral-hit clones. Same core loop, same art style, a name that puns on the original.
- Unofficial clients and wrappers that put another company's website or API into an app with that company's logo and colors. Guideline 5.2.2 also requires permission under the third-party service's terms, and Apple can ask for proof.
- Competitor names in metadata. Subtitles, keywords or descriptions that reference other apps also break 2.3.7 (see Guideline 2.3 Accurate Metadata).
- Your own product, different publisher. The web or Google Play version ships under another legal entity, so the iOS app looks like someone copied you.
- Agency submissions where a client's branded app is published under the agency's developer account.
- Third-party characters or logos in screenshots, onboarding or the launch screen.
Rejected or stuck? Talk to an App Specialist – for free.
Book a free consultation call: we look at your rejection or setup, explain the fastest way forward and tell you honestly whether you need us. Prefer to hand it off? Book our AI-powered + human-powered service and we take care of it.
How Apple distinguishes inspiration from copying
Apple publishes no similarity threshold – it is a reviewer judgment. Sharing a category or genre is not what 4.1 targets (saturated categories are a Guideline 4.3 Spam topic). What triggers 4.1 is a combination of borrowed identity signals that makes your app easy to mistake for one specific product. In its forum post Preventing Copycat and Impersonation Rejections, the App Review team specifically warns against copying the look and feel or UI design of other apps.
| Usually fine (inspiration) | Likely 4.1 (copying) |
|---|---|
| Same genre or mechanic (match-3, habit tracker, word puzzle) | Same mechanic plus the layout, colors and name pattern of one specific hit |
| Standard iOS components: tab bars, lists, SF Symbols, system sheets | Close reproduction of another app's signature screens |
| Descriptive name that says what the app does | Name containing another product's name or a near-homophone |
| Your own icon concept and palette | Recolored or slightly altered version of a famous icon |
| A service you have permission to use, labeled honestly | Presenting yourself as that service's official app |
A quick self-test: show your icon and name, without context, to someone who doesn't know your project. If their first guess is another app or company, App Review may well make the same association. For actual trademark questions, talk to an IP lawyer.
How to fix a Guideline 4.1 rejection step by step
- Find out what you were compared to. If the message doesn't name the reference app or element, reply in App Store Connect and ask which app and which elements (name, icon, UI, screenshots) caused the concern.
- Audit every surface. In App Store Connect: app name (30-character limit), subtitle, keywords, promotional text, description, screenshots and app previews. In the binary: app icon and alternate icons,
CFBundleDisplayNameinInfo.plist, launch screen, onboarding, in-app strings and bundled images. Also check your developer name, support URL and website – Apple asks for account and app information that is current, accurate and verifiable. - Rename if the name borrows anything. Remove other brands, product names and near-homophones. Under 4.1(c), "for [Brand]" is not a loophole.
- Redesign the icon from a new concept instead of recoloring it. Replace the
AppIconset in your Xcode asset catalog (or your.iconfile if you use Icon Composer). The icon ships inside the build, so this requires a new build with an incremented build number (CFBundleVersion). - Differentiate the UI that reviewers see first: the screens in your screenshots and the first-run flow. Change palette, layout, typography and the signature interaction. If the core loop is genre-standard, make the presentation unmistakably yours.
- Remove or license third-party assets – logos, characters, fonts, sounds – unless you have written permission.
- Lead with your unique features in the first screenshots and the first lines of the description.
- Resubmit with context. Upload the new build, select it on the version page, summarize the changes in the App Review Information Notes field (up to 4,000 bytes), reply to the rejection message and submit for review.
If you are the legitimate owner or licensee
Sometimes the "copy" is you: the original web game, the brand's official app, or an app built under license. Then don't redesign – prove your rights. Guideline 5.2.1 says apps should be submitted by the person or legal entity that owns or has licensed the intellectual property and other relevant rights.
Documents that help
- Trademark registration certificates in the name of the account holder's legal entity.
- A signed authorization letter from the brand owner naming the app, your developer account's legal entity, the permitted use (name, icon, content), territory, term and a contact for verification.
- Relevant excerpts of a license or distribution agreement.
- Proof you published the original: your official website linking to the App Store listing, or a Google Play developer page under the same entity.
Attach the files when you reply to App Review and mention them in the App Review Information notes for future submissions. Never submit altered or unverifiable documents: App Review states that accounts submitting fraudulent documentation will be removed from the Apple Developer Program.
Fix the account structure, too
- Agencies: publish under the client's own Apple Developer Program account, with your team added as users (for example with the Admin or App Manager role), not under your own developer name.
- Moving an existing app to another company: use App Transfer in App Store Connect, which keeps the bundle ID, ratings and reviews, instead of resubmitting a duplicate. Check Apple's transfer criteria first.
- White-label or template apps for many clients run into Guideline 4.2.6 (template apps must be submitted by the provider of the app's content) and 4.3 Spam – each client should own its listing.
Responding to App Review and appealing
In App Store Connect, select your app, click the link indicating unresolved issues, choose Resolve next to the submission, then Reply to App Review. Replies are limited to 4,000 characters and can include files via Attach File. You need the Account Holder, Admin or App Manager role.
- Ask for clarification when the reference app or element is unclear.
- Reply with changes after rebranding: list each change (old to new name, new icon, redesigned screens) and resubmit.
- Reply with documentation when you own or license the brand.
- Appeal to the App Review Board via the appeal form if you believe the reviewer misunderstood your app. Apple asks for specific reasons why the app complies, allows one appeal per rejected submission, and expects open information requests to be answered first.
Pointing out that similar apps are already on the store rarely helps, and neither do claims of originality without evidence. A short list of features the reference app lacks, plus side-by-side screenshots, is far more persuasive. You can also request a 30-minute video appointment with App Review (subject to availability) to discuss the rejection.
For apps already live, Apple's bug-fix process does not delay bug fixes over guideline violations except those related to legal or safety issues. Impersonation and IP findings can fall into the legal category, so don't count on that route here.
How to prevent copycat rejections in future releases
Most 4.1 problems are baked in at the naming and design stage:
- Name search: check the App Store and Google Play for your planned name and variants, and run a trademark search (for example in the USPTO, EUIPO or WIPO databases) before committing.
- Metadata in version control: keep name, subtitle, keywords and descriptions in your repo (fastlane
deliveror the App Store Connect API) and add a CI step that fails when a denylist of third-party brand and competitor names appears. - Visual review: compare your icon and first three screenshots against the top apps in your category before every rebrand.
AI-assisted checks are good at flagging brand terms and visual similarity at scale; a human still has to judge the overall impression. That is how appsubmitter.io works: AI-powered checks plus experienced App Specialists who review your listing, handle submission and review communication, and guide you through rejections like this one (design or code changes are discussed and quoted upfront). Unsure whether your branding is too close to another app? Book a free consultation call before you submit, or book the service to have us run the submission end to end.
Guideline 4.1 vs. 5.2.1, 4.3 and Google Play
| Guideline | Core question | Typical fix |
|---|---|---|
| 4.1 Copycats | Does the app pose as, or look confusingly like, another app or service? | Rebrand and redesign, or prove authorization |
| 5.2.1 Intellectual Property | Do you have rights to the trademarks and content you use? | Remove the material or provide licenses |
| 4.3 Spam | Is the app indistinguishable from what is already widely available, or a duplicate of your own apps? | Consolidate apps, differentiate meaningfully |
| 2.3.7 Metadata | Is the metadata packed with trademarked terms or popular app names? | Clean name, subtitle and keywords |
Google Play has a separate Impersonation policy: it doesn't allow apps that mislead users by impersonating another developer, company, entity or app, including falsely implying a relationship or using icons and titles so similar to existing products that users may be confused. See our guide to the Google Play metadata policy for the store listing side. Roll out any rebrand on both stores so your listings stay consistent.
Template: how to reply to App Review
Adapt this template to your situation. Keep it factual, short and specific – and only claim what you have actually changed.
Hello App Review Team, Thank you for reviewing [App Name] (version [x.y], build [build number]) and for your feedback regarding Guideline 4.1 - Design - Copycats. [Option A – changes made] We have revised the app and its metadata so it can no longer be mistaken for [reference app]: - App name changed from "[old name]" to "[new name]"; subtitle and keywords no longer reference other apps or brands. - New app icon based on an original concept (included in build [build number]). - Redesigned [main screen / onboarding] with our own color palette, layout and typography. - Removed all third-party logos and characters from screenshots and in-app content. Distinguishing features: [feature 1], [feature 2], [feature 3]. [Option B – we are the rights holder or licensee] [Legal entity name], the account holder, is the [owner / authorized licensee] of [brand / app]. Attached: [trademark registration / signed authorization letter from (rights holder) dated (date) / license excerpt]. Verification contact: [name, email]. If anything still raises concerns, could you tell us which app we are being compared to and which element (name, icon, UI or screenshots) is affected? We will address it right away. Best regards, [Your name] [Company]
Checklist before you resubmit
- You know which app or service the reviewer compared you to, and which elements were flagged.
- App name and subtitle contain no other developer's brand, product name or near-homophone.
- Keywords, promotional text and description mention no competitor apps or third-party brands.
- The icon is a new original concept; alternate icons and CFBundleDisplayName are updated in the new build.
- Screenshots, previews, launch screen and onboarding show no third-party logos, characters or look-alike UI.
- Developer name, support URL and website are current and match the brand shown in the app.
- If you use a brand under license, signed authorization or trademark documents in the account holder's entity name are ready to attach.
- The App Review Information notes summarize all changes, and the build number has been incremented.
Frequently asked questions
What does "Guideline 4.1 - Design - Copycats" mean?
Can I use another app's name in my app name if I add "for" or "unofficial"?
Is it a copycat violation to make an app similar to a popular one?
I am the original developer – why was my app flagged as a copycat?
Do I need a new build to fix a 4.1 rejection?
Can a 4.1 rejection affect my developer account?
Official source: App Store Review Guidelines – 4.1 Copycats. Store policies change regularly – always check the current version. This guide is independent advice and not affiliated with Apple or Google.