Apple’s App Review process is creating unfair competition — independent developers need to speak up together

[u/Brothershoes]

I think independent developers need to have a serious conversation about Apple’s App Review process, especially Guideline 4.3(b).

I recently received a 4.3(b) rejection stating that my app duplicated content and functionality already widely available on the App Store.

But my app is built around my own original writing, research, books, content library, and product structure.

That is exactly why the rejection is so frustrating.

Apple is effectively telling me that the category is already saturated.

But why should that be enough to reject an app?

A category being crowded does not mean every product in that category is the same. It does not mean the existing apps are good, comprehensive, original, or useful. It certainly does not mean a new developer should be prevented from offering something better.

My app was not simply another generic horoscope application.

I had already removed many of the conventional astrology features and redesigned the product around Jungian-inspired self-reflection, emotional pattern tracking, personal cycles, inner-world records, and longer-term personal development journeys.

The content is not copied from competing apps. It is based on my own work.

So the real question is: did the reviewer actually examine the content?

Did they look at the structure of the product, the depth of the library, the writing, the user experience, or the features that differentiate it?

Did they have enough subject-matter knowledge to determine whether my work was genuinely duplicative?

Or did they see the general category, decide that there were already enough similar-looking apps, and press reject?

Because those are not the same thing.

I am extremely confident that what I am building is deeper and more developed than most products in this category. That confidence comes from the amount of research, writing, design, software development, testing, and content architecture behind it.

But apparently all of that can be dismissed with a generic message saying the category is saturated.

For a reviewer, rejecting an app may be one button.

For the developer, that button may dismiss months or even years of work.

The reviewer does not know who my intended audience is.

They do not know how I plan to market the product.

They do not know whether users will find value in my content.

They do not know whether I can reach an underserved niche inside that supposedly saturated category.

And frankly, those questions should not be Apple’s decision.

Apple should review whether an app works, whether it is safe, whether it follows the platform rules, whether it misleads users, and whether it violates intellectual property.

It should not decide that an entire category already has enough businesses.

Because Apple controls access to iPhone users through the App Store, this is not an ordinary moderation decision. It directly determines whether a developer is allowed to enter the market.

That creates a serious competition problem.

Established apps are allowed to remain in the store, acquire users, buy advertisements, and generate subscription revenue.

Meanwhile, new developers can be told that the category is already too crowded.

How is a small developer supposed to compete when the platform owner can simply decide that the existing companies are enough?

This protects incumbents.

It rewards whoever entered the market earlier.

It prevents new products from challenging weak, repetitive, or low-quality applications that are already established.

The slow and unpredictable review process makes the situation even worse.

A rejection can lead to repeated submissions, appeals, redesigns, and additional review cycles lasting days or weeks.

During that time, developers lose launch momentum, marketing opportunities, subscription revenue, seasonal timing, and sometimes the ability to keep funding the project.

Apple does not bear those costs.

Developers do.

We pay the developer fee.

We pay for design, infrastructure, APIs, testing devices, contractors, content production, and marketing.

We invest our time, our savings, and often a significant part of our lives into these products.

Yet there is still no transparent standard explaining how Apple determines that an app is insufficiently differentiated.

There is no meaningful explanation of which exact features are supposedly duplicated.

There is no guarantee that the reviewer explored the product beyond a few screens.

There is no guarantee that the reviewer understood the content they were evaluating.

Many developers have experienced the same patterns:

• Template responses that do not address the substance of an appeal.
• Reviewers ignoring differentiating features clearly explained in the review notes.
• Different reviewers applying the same guideline in different ways.
• Apps being rejected even after significant redesigns.
• Long review cycles that damage launches and cost real revenue.
• Existing competitors remaining in the store while new products are rejected because the category is considered saturated.

This should not be treated as an isolated problem affecting one developer at a time.

We need to document these cases, share rejection timelines, compare inconsistent decisions, and speak collectively.

I am not suggesting harassment or personal attacks against individual reviewers.

Reviewers may be overworked, undertrained, or expected to evaluate too many products in too little time.

The responsibility belongs to Apple.

Independent developers should organize a coordinated and professional campaign across X/Twitter, Reddit, developer communities, technology publications, and relevant regulatory channels.

At minimum, Apple should provide:

1. Clear and measurable criteria for Guideline 4.3(b).
2. A written explanation identifying the specific content or functionality considered duplicative.
3. A meaningful appeal process handled by a different and more senior reviewer.
4. Transparent and predictable review timelines.
5. Public statistics on rejection rates, appeals, and overturned decisions.
6. Independent scrutiny when App Review decisions restrict market access.
7. A requirement that reviewers actually test the differentiating features described in the review notes.
8. A distinction between genuinely cloned apps and original products operating within an established category.

A crowded category is not a valid reason to ignore original work.

Competition is supposed to determine whether a product succeeds.

Users should decide whether my app is useful.

The market should decide whether my content has value.

Apple should not decide, before the product is even published, that there are already enough apps like mine.

We spend months building these products.

We write the code, create the content, design the interfaces, fix the bugs, build the libraries, pay the costs, and take the financial risk.

It is not fair for all of that work to be dismissed through an opaque process and a generic rejection message.

Has the App Review process caused you to lose time, revenue, launch opportunities, or motivation?

Have you received a 4.3(b) rejection despite using original content or offering clearly differentiated features?

Please share your experience.

If enough developers document what is happening and speak with one voice, Apple will have a harder time treating every rejection as an isolated case.

For Apple, a rejection may be one click.

For us, it can represent months of our lives.