I want to add a concrete example from my own experience with a game I developed, which was rejected under Guidelines 4.3 and 4.2.6.
The idea for this game came from my son. We worked on it together and playtested it together, with his feedback helping shape the UX and game design. It is a standalone family project, with no significant code or assets reused from my other apps or a third-party game or template.
The rejection lists possible types of spam, but does not identify which specific content or functionality was duplicated, which existing app it considers indistinguishable, or what evidence supports the reference to an app generation service. It then warns against resubmitting without substantial improvements and asks nine detailed questions about the product, audience, testing, code sharing and ownership.
I am willing to explain all of those things. What frustrates me is the imbalance: developers are asked for detailed, specific answers, while the rejection itself gives us broad possibilities instead of a specific finding. How can we make meaningful improvements when we are left guessing what the reviewer believes is wrong?
I am angry and disappointed. Having something my son and I worked on together labelled spam without a concrete explanation feels dismissive and disrespectful of our effort. The uncertainty also makes it difficult to decide where to spend more development time.
A fair review process should identify the issue, explain how the cited guideline applies to the submitted app, and give the developer an actionable way to respond. Shared genre conventions should be assessed alongside the actual implementation and experience. Independent developers need clear reasons and consistent criteria to understand the decisions affecting their work.
Has anyone managed to get a specific explanation of a 4.3 rejection, particularly when 4.2.6 is also cited despite the app being independently developed? What helped move the discussion beyond a generic rejection?
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags: