AppReviewDebug

LanguageEN中文

Guideline4.3

Guideline 4.3 Similar Concept: What Apple Is Flagging

§ 01What this rejection usually means

Similar concept is the softest and the most frustrating 4.3. Apple is saying the product idea sits in a pile of lookalikes: AI wrappers, VPN skins, locker apps, photo toolkits, white-label shops.

§ 02What Apple’s wording tells you

App Review
Your app shares a similar concept with apps submitted to the App Store.
App Review
We noticed your app shares a similar binary, metadata, and/or concept with apps submitted to the App Store.

They are not primarily complaining about your plist. They cannot see a reason this app should exist next to the others they have already reviewed.

§ 03Common causes

  • A crowded category with no durable difference in the first session.
  • The same three tabs every template ships: home, generate, settings.
  • Positioning that is only a theme or a celebrity skin on a generic tool.
  • Several concept-clones already submitted from your account or your contractor.

§ 04How to diagnose your case

  1. Write the difference in one sentence that does not use the words AI, better, or easier.
  2. If you cannot, this is a product problem, not a review-note problem.
  3. If you can, put that difference in the first screenshot and the reply.

§ 05What to inspect in your project

  • First-run path: is the unique feature unavoidable?
  • Tab bar and information architecture vs. the default template
  • Empty states and sample content — yours or the vendor’s?
  • Description’s first paragraph vs. the actual home screen

§ 06What not to do

  • Do not add a second skin and call it differentiation.
  • Do not file an appeal that says “the category is allowed.” Allowed is not the same as distinct.
  • Do not submit three concept variants from one account.

§ 07How to fix it

  1. Move the unique workflow to the first screen.
  2. Remove template chrome that signals “another one of these.”
  3. Rewrite metadata around the specific job, not the category.

§ 08How to verify the fix

  • A reviewer who spends ninety seconds on the home screen should hit the unique action.
  • Compare that path to the two closest competitors.

§ 09What evidence to prepare

  • A short feature comparison that is specific, not marketing
  • Design history that shows the unique flow was intentional
  • Any user research or existing users you can describe without leaking PII

§ 10Suggested reply to App Review

Resolution Center · Reply
Hello App Review,

This app is in a busy category, but the product is not a reskin of a generic tool.

The core job is [specific job]. In the first session a reviewer will: 1) [step], 2) [step], 3) [unique outcome]. That path is not present in a standard template.

We updated screenshots so this path is visible immediately. We are not submitting multiple concept variants of the same binary.

Thank you.

§ 11Should you appeal?

Concept 4.3s rarely win on appeal unless you can show a reviewer skipped the unique flow. Make that flow obvious first.

§ 12Questions people ask next

Can a photo or AI utility ever pass 4.3?
Yes, if the first session is a specific job and the listing does not look like the last twenty. Category alone is not the rejection.

Related scenarios

Related rejection wording