Publications

How to Remove a Copycat App from the App Store or Google Play

A copycat app can do more than imitate a successful product. It can appear in searches for the original app, divert potential customers, damage the original developer’s reputation, and make users believe the two products are connected.

Apple and Google both prohibit apps that copy or impersonate existing products. But neither platform automatically removes an app merely because a developer calls it a copycat. The complaint must identify the specific similarities, connect them to the platform’s rules, establish the complainant’s rights, and request a concrete remedy.

We have also published a Guide to App Store Disputes for Developers, which explains the most common types of disputes with Apple, Google, and competing developers, the available internal processes, and possible legal options when those processes fail.

Our expertise in Platform & Developer Disputes

We act for app developers, platform-based businesses, and digital product companies in disputes with major online ecosystems such as app stores, social networks, and online service platforms. We challenge wrongful takedowns and suspensions, escalate and review moderation decisions, seek reinstatement of apps and accounts, and handle IP and commercial disputes on and off platform.

Learn more about our experience in Platform & Developer Disputes

What Counts as a Copycat App?

The strongest copycat-app complaints usually involve several overlapping elements, such as:

  • the same or a highly similar app name; 
  • an icon with similar lettering, colors, shapes, or layout; 
  • copied screenshots, preview materials, or product descriptions; 
  • use of another developer’s trademark in the title, subtitle, keywords, or other metadata; 
  • a similar user interface or overall visual presentation; 
  • statements suggesting that the app is official, authorized, or affiliated with another company; or 
  • search placement that puts the copycat app in front of users looking for the original product. 

Similar functionality alone may not be enough. Many apps compete in the same category and offer comparable features. The argument becomes stronger when the competing app copies the public-facing identity of an existing product: its name, icon, branding, metadata, screenshots, or presentation.

What Apple’s Rules Say About Copycat Apps

Apple’s App Review Guideline 4.1 directly addresses copycat and impersonator apps1. It prohibits developers from making minor changes to another app’s name or user interface and passing the result off as their own. It also states that developers cannot use another developer’s icon, brand, or product name in an app’s icon or name without approval. 

Apple has reinforced that rule in its official App Review guidance. Apple states that apps that actively try to copy other apps will not pass review and that accounts repeatedly submitting copycat or impersonator apps may be closed. Apple also warns developers not to copy another app’s look and feel or imitate its features and functionality. 

Several other Apple rules may apply:

  • Guideline 5.2 — Intellectual Property: Apps may be removed for using content without permission. Apple specifically prohibits unauthorized use of trademarks and misleading, false, or copycat names and metadata. 
  • Guideline 2.3.7 — Metadata: Developers must choose a unique app name and may not pack metadata with trademarked terms or popular app names to game the system. 
  • Guideline 5.6.3 — Discovery Fraud: Manipulating search, charts, reviews, referrals, or other parts of the App Store customer experience is prohibited. 
  • Guideline 4.3 — Spam: Apple prohibits opportunistic variants of existing apps that degrade App Store discovery and harm users and developers. 

Apple’s official guidance also says that leveraging another app’s popularity through protected content or irrelevant brand references in metadata is misleading. 

A developer who believes an App Store listing violates its intellectual property rights can submit an App Store Content Dispute2. Apple states that it will generally contact the provider of the disputed app and ask the parties to work directly toward a resolution. Apple also has a separate App Name Dispute process where another app is preventing a trademark owner from using its mark as an App Store name3

What Google Play’s Rules Say About Copycat Apps

Google Play addresses copycat apps primarily through its Impersonation Policy and intellectual property reporting processes.

Google prohibits developers from falsely implying a relationship with another company, developer, organization, or app. Its examples include apps whose icons and titles are so similar to existing products that users may be misled, apps that copy a business logo to appear official, and apps that falsely claim to be the official app of an established entity4

Google distinguishes between several possible complaint routes:

  • an impersonation report, where the app misleads users about its connection to another developer or company; 
  • a trademark complaint, where the app uses protected branding without authorization; 
  • a copyright complaint, where the app copies protected artwork, screenshots, text, code, or other content; or 
  • another legal-removal request where a different legal right is involved. 

Google warns that using the wrong reporting process may delay or prevent the complaint from being handled. 

Evidence to Collect Before Filing a Copycat-App Complaint

A successful complaint should make the problem easy for the platform reviewer to understand. The reviewer should not have to search for the original app, reconstruct the timeline, or guess which parts of the competing listing are objectionable.

Because the outcome may turn on how the facts, platform rules, and legal rights are presented, having a lawyer draft or review the platform complaint and related communications can help ensure that the submission is focused, supported, and directed to the correct platform process.

The evidence package should normally include the following.

1. Proof of Ownership and Prior Use

Provide the records showing that your company owns or has the right to use the relevant name, branding, and content. Depending on the dispute, this may include:

  • trademark registrations or applications; 
  • copyright registrations; 
  • domain registration and website records; 
  • original design files; 
  • dated marketing materials; 
  • app-release and version history; 
  • source-control history; and 
  • invoices or agreements showing when the branding was created. 

A registered trademark can be important, but the timeline should not begin and end with the registration date. Evidence showing when the app, website, and brand entered commercial use may also be relevant.

2. Side-by-Side Comparisons

Place the two app listings next to each other. Compare the:

  • app names; 
  • subtitles; 
  • icons; 
  • color schemes; 
  • screenshots; 
  • preview videos; 
  • descriptions; 
  • keywords; 
  • interfaces; and 
  • product claims. 

Label each side so the reviewer can immediately identify the original app and the competing app.

3. Search and Discovery Evidence

Capture screenshots showing what happens when a user searches for your brand on the App Store, Google Play, or the web.

This evidence can be especially important where the copycat app:

  • appears above the original app; 
  • uses the brand name in its title or subtitle; 
  • uses a store URL containing the brand name; 
  • appears in web search results for the original product; or 
  • otherwise benefits from traffic intended for the original developer. 

This does not necessarily prove that specific users were confused. It does show the risk of traffic diversion and the way the competing app is presented to users searching for the original product.

4. Evidence of Actual or Potential Brand Harm

Preserve customer emails, support requests, reviews, social-media posts, and other records showing that users associated the competing app with your company.

Actual customer confusion is useful when available, but a complaint should not claim it exists unless there is evidence. Other records may still show the potential harm. For example, an app using your name may have poor ratings, repeated complaints that it does not work, or reviews describing it as fraudulent. Those reviews do not by themselves prove confusion, but they may show the reputational risk created by allowing a low-quality app to operate under confusingly similar branding.

5. A Detailed Timeline

Prepare a short chronology covering:

  • when your app and website launched; 
  • when you began using the disputed name; 
  • when the competitor’s app appeared; 
  • any relevant title or branding changes; 
  • when the complaint was submitted; and 
  • what each party said or did afterward. 

A timeline becomes particularly important if the competing developer claims that it used the name first or argues that your own branding changed over time.

6. The Exact Remedy Requested

Do not ask only for “appropriate action.” State what would resolve the dispute.

Depending on the facts, the requested remedy may include:

  1. removal of the app; 
  2. removal of the disputed name from the title and subtitle; 
  3. removal of the mark from keywords, descriptions, and other metadata; 
  4. adoption of a different icon and branding; 
  5. replacement of copied screenshots or preview materials; 
  6. removal of the disputed branding from inside the app; and 
  7. correction of any store URL or other user-facing identifier that continues to display the disputed name. 

Specific requests make it easier for the platform and the other developer to understand what must change.

How the Copycat-App Dispute Process Usually Works

The platform may remove the app immediately, request additional documentation, or forward the complaint to the other developer and ask the parties to resolve the matter directly.

The competing developer may deny the claim, question the trademark’s scope, challenge the timeline, or offer partial changes. The complainant should keep the focus on the current public presentation of the app and the exact platform rules being violated.

Verify Claimed Changes Before Agreeing That the Dispute Is Resolved

Where the competing developer offers to rename or rebrand the app, do not confirm that the matter has been resolved based only on a written promise. The same rule applies where the developer claims that the changes have already been completed. Before telling Apple or Google that the dispute is resolved or agreeing that the app may return to the store, ask for evidence showing exactly what was changed.

Ask to review:

  • the proposed title and subtitle; 
  • the revised icon; 
  • the revised screenshots and previews; 
  • the updated metadata; 
  • the in-app interface; and 
  • any remaining use of the disputed name. 

The evidence should ordinarily include screenshots from App Store Connect or Google Play Console, the revised store listing and preview materials, and screenshots from inside the updated app. A general statement that the name, branding, or metadata has been changed is not enough to verify that the copycat problem has actually been fixed.

A title change may not resolve the problem if the icon, metadata, screenshots, or other branding remain confusingly similar. The same applies where a store URL continues to contain the disputed brand. That issue should be raised expressly because it may require action by the platform as part of approving or publishing the revised listing.

Where a field cannot be changed by the developer, ask the developer to identify the technical restriction and raise the issue directly with the platform. Distinguish between backend identifiers that users never see and user-facing elements, such as the store URL, that may continue to affect search visibility, traffic diversion, or customer perception.

Common Mistakes in Copycat-App Complaints

Several recurring mistakes make these disputes harder to resolve.

Filing a General Complaint Without Identifying the Rule

A complaint should explain exactly how the app violates the platform’s copycat, impersonation, metadata, or intellectual property rules.

Relying Only on Similar Functionality

Competing apps often have similar features. Focus on copied names, icons, metadata, screenshots, interfaces, and branding.

Failing to Address the Other Developer’s Timeline

If your app has changed names or branding, explain why. Show how the website, mobile app, user accounts, backend, and commercial product fit together.

Confirming Resolution Too Early

Once the complainant tells the platform that the dispute is resolved, the app may be reinstated. Confirm the revised materials first and state any remaining conditions in writing. Do not rely only on the competing developer’s description of the changes. Require evidence and review the actual revised app, listing, branding, metadata, and screenshots before supporting reinstatement.

Allowing the Matter to Sit

Copycat apps can gain rankings, reviews, backlinks, and search visibility over time. Preserve the evidence and act before the competing listing becomes more established.

What Developers Should Do Now

Developers who discover a copycat app should:

  • capture the competing listing before it changes; 
  • document their ownership and prior use; 
  • prepare labeled side-by-side comparisons; 
  • preserve search-result evidence; 
  • identify the correct Apple or Google policy; 
  • file through the correct platform process; 
  • request specific corrective changes; 
  • require evidence of any claimed corrective changes before agreeing that the matter is resolved; and 
  • keep a complete record of all platform and developer communications. 

When the platform process stalls, the next step may be a demand letter, direct negotiation, or litigation against the competing developer. The appropriate escalation depends on the strength of the intellectual property rights, the location of the parties, the commercial harm, and the platform’s response.

How We Can Help

Our App Store and Tech Platform Disputes practice represents app developers, digital product companies, and platform-based businesses in copycat-app, impersonation, trademark, and app-removal disputes. We have experience representing developers in copycat-app disputes, including securing the removal of infringing apps and, where appropriate, resolving the dispute through changes to the competing app’s name, branding, metadata, or presentation.

We prepare submissions to Apple and Google, organize technical and intellectual property evidence, negotiate corrective changes with competing developers, and are prepared to escalate disputes through demand letters or litigation when platform procedures do not resolve the dispute.

Developers dealing with a copycat app, misleading App Store listing, or Google Play impersonation issue can submit a request through our intake form

Sources & References

  1. App Review Guidelines, developer.apple.com; Preventing Copycat and Impersonation Rejections, https://developer.apple.com/forums/thread/782175.
  2. App Store Content Dispute, https://www.apple.com/legal/intellectual-property/dispute-forms/app-store/
  3. App Name Dispute, https://www.apple.com/legal/intellectual-property/dispute-forms/app-store/app-name-dispute.html
  4. Play Console Help – Impersonation, https://support.google.com/googleplay/android-developer/answer/9888374?hl=en.
 

Contacts

Thank you for your application!

We will contact you shortly.
Oops! Something went wrong while submitting the form.