AppReviewFix
Guideline library
Google Play — Trust & Safety

System UI Imitation — Unauthorized imitation of system UI

Official source: Google Play Developer Program PoliciesTopic overview: Spam, copycat apps, ads and deceptive design explained
What this guideline means

This prohibits apps from mimicking Android's actual system UI — fake "low battery," "virus detected," or permission dialogs — in a way that could trick a user into believing they're interacting with the operating system rather than a third-party app.

Why apps actually get flagged

Common in "cleaner" or "booster" utility apps that show a fabricated system warning to scare the user into taking an in-app action, like upgrading to a paid tier.

A real example

"Your app displays a user interface that imitates a system warning or notification to deceive users into taking an action, per the Unauthorized Use or Imitation of System Functionality policy."

The short version, in more detail

This policy prohibits apps from imitating Android's own interface, such as fake low-battery messages, virus warnings or permission dialogs that could make a user think they are dealing with the operating system. Cleaner and booster utilities that display a fabricated system warning to push people toward a paid upgrade are the typical example.

Why this rule exists

People trust the operating system to tell them the truth about their device. If an app can create something that looks like a system alert, the user cannot tell whether a message is real, which makes scams and manipulation much easier. Keeping system-style interfaces reserved for the system protects the one source of messages users have most reason to believe.

What this guideline covers

  • Fake system warnings, notifications and dialogs.
  • Interface elements that mimic Android's design for deception.
  • Alerts used to pressure users into actions.
  • Permission and security screens that are not genuine.

What usually triggers this rejection

  • A cleaner showing a fabricated virus warning.
  • A notification that looks like a system alert.
  • A fake permission dialog.
  • A battery warning used to sell an upgrade.
  • Overlays that resemble the system interface.

How reviewers evaluate it

  • Reviewers compare in-app alerts with real system UI.
  • They look at the purpose of the message.
  • Automated systems flag known deceptive patterns.
  • User reports contribute.

Common misunderstandings

  • A design that borrows the system look to seem official is a problem even if the message is mild.
  • Following Material Design is fine. Pretending to be the system is not.
  • The effect on the user matters more than the developer's intent.

Common questions

Can my app use system-style dialogs?

It can use standard components, but not in ways that pretend to be the operating system.

Is this related to social engineering?

Yes. They overlap in cleaner and booster apps.

Do notifications count?

Notifications that imitate system alerts do.

Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current Google Play Developer Policy Center for the exact wording.

Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.
Decode my rejection
Related guidelines
2.5.18 — Display advertising limitations3.2.2 — Unacceptable business models4.5.4 — Push notification abuseAds — Ads policyAd Fraud — Ad fraud (Mobile Unwanted Software)
AppReviewFix
ProductDecoderPricingGuideline library
CompanyAboutFAQContact
ResourcesGuidesTopic overviewsCommon rejection reasons
LegalTermsPrivacy
© 2026 AppReviewFixBuilt by a developer, not a committee.