A Competitor's App Got Approved and Mine Was Rejected — Now What?
It's one of the most frustrating moments in app development: your submission gets rejected under a specific guideline, and then you find a live app on the store doing exactly the thing you were told you couldn't. Surely that proves you should be approved too? Unfortunately, that's not how App Review works — and understanding why saves you a lot of wasted energy.
Approval Is Not Precedent
The App Store doesn't operate on case law. Each submission is evaluated on its own against the guidelines as they stand at that moment. The fact that another app was approved doesn't create a rule that your app must be approved too. Reviewers aren't comparing your submission to a catalog of what's already live; they're checking your app against the guideline.
So when you write "but App X does this and it's on the store," you're not presenting the strong argument it feels like. At best it's ignored. At worst it distracts from the actual issue — the specific thing about your app that triggered the rejection — and makes your appeal weaker.
Why That Competitor Is Still Up (For Now)
Here's the part developers underestimate: being approved once doesn't mean staying approved.
Guidelines change, and enforcement changes with them. New policies frequently roll out after a wave of apps has already been approved under the old rules. When that happens, those apps aren't automatically grandfathered in — they're expected to update to meet the new policy. Apple periodically circles back through the store and removes apps that no longer comply.
That means the "competitor who got away with it" may simply be an app that:
- Was approved under older rules that have since tightened
- Slipped through and hasn't been re-examined yet
- Is on a list to be pulled the next time policy enforcement sweeps its category
An app being live today is a snapshot, not a guarantee. Building your own strategy around "they did it, so I can too" is building on ground that can disappear.
You Can't See the Full Picture
Even setting enforcement aside, you usually can't see why the other app was approved. What looks identical from the outside may differ in ways that matter:
- Different entitlements granted by Apple
- Different App Review Notes that framed the functionality differently
- A different account history or private communication with the review team
- A different submission date under different policy
From the store listing, all of that is invisible. So the apparent inconsistency often isn't inconsistency at all — it's missing context. Judging your own path by another app's surface appearance means reasoning from incomplete information.
What to Do Instead
Redirect the energy you'd spend comparing yourself to competitors back onto your own submission:
- Read the exact guideline cited. Not the general category — the specific number and its wording.
- Address that guideline directly. Change the app or its positioning so the concern no longer applies. (If your rejection was under Guideline 4.3, our guide on surviving Guideline 4.3 walks through concrete repositioning tactics.)
- Strengthen your notes and demo account so the reviewer can clearly see your app complies. See what to put in your App Review Notes.
- Appeal on the merits if you genuinely believe the guideline was misapplied to your app — not on the basis that someone else got approved. Our guide on how to appeal an App Store rejection covers how to make that case.
The Mindset Shift
The instinct to point at competitors comes from a fair place — it feels unfair. But App Review isn't a court weighing precedent; it's a checkpoint applying current policy to your specific app, with enforcement that catches up to stragglers over time. The app you're envying may be living on borrowed time. The most reliable way out of a rejection is almost always the least satisfying one: stop watching the other app, and fix your own.
Once You're Live, Stay Ahead of Your Reviews
Getting approved is only half the battle — keeping your rating healthy is the other. AppStoreReview monitors your app across 175+ countries, sends instant alerts for new and negative reviews, and lets you filter by keyword so you catch problems early.
Frequently Asked Questions
A competitor's app does the same thing mine was rejected for — can I use that in my appeal?
You can mention it, but don't build your case around it. Every submission is evaluated on its own, and 'another app does this' is not treated as precedent. Pointing at competitors rarely changes a decision and can distract from the real fix. Focus your appeal on why your app complies with the specific guideline cited, not on what someone else got away with.
Why do some non-compliant apps stay on the App Store?
Approval isn't a permanent guarantee. Guidelines and enforcement evolve, and apps that were approved under older rules — or that slipped through — get re-examined later. Apple periodically circles back and removes apps that no longer meet current policy. So an app that looks like it 'got away with it' today may simply not have been caught yet.
Does seeing a similar approved app mean my rejection was a mistake?
Not necessarily. Review outcomes can look inconsistent because different submissions are handled at different times under evolving policy, and because you often can't see the full context of the other app — its entitlements, its App Review Notes, its history, or private communication with Apple. A visible similarity on the store doesn't tell you why the other app was approved.
What should I do instead of comparing my app to competitors?
Put your energy into your own submission: read the exact guideline cited, address it directly, strengthen your App Review Notes and demo account, and if you genuinely believe the guideline was misapplied, appeal on those grounds. A focused fix to your own app resolves rejections far more reliably than arguing about someone else's.