If App Review rejected your app under Guideline 4.3 (Design – Spam), sometimes together with 4.2.6 (App Generation Services), it is not a bug report. It is a comparison. Reviewers are saying your app looks too much like other apps on the store, or like a template, and that the difference is small. Quality is not the question; distinctiveness is.
This comes from our own review history: we ship a portfolio of small Mac and iPhone apps, and a single-purpose utility of ours received a 4.3(a) rejection that took a little over a month to turn around. What follows is the order that worked, and why each step comes where it does.
What 4.3 actually measures
Guideline 4.3(a) is about an app that is similar to other apps in its binary, metadata or concept, with only minor differences. 4.3(b) is about apps that crowd a category that already has plenty of them. 4.2.6 adds the template angle: an app that looks produced in bulk from a template or a generation service.
None of this shows up locally. Builds, tests, metadata checks and screenshot rendering all compare your app with its own spec. 4.3 compares it with everyone else's apps, which are not in your repository. A green CI run and a 4.3 rejection do not contradict each other.
The order that worked
- Do not argue with the word "spam". It does not mean you copied code. Re-read the rejection and work out which of the three tests you hit: binary, metadata or concept. If you started from a shared template or a purchased source project, the binary similarity is measurable. If your description and screenshots read like a template, metadata is the one that fired.
- Be honest about whether it is a near-copy. Search the App Store for your two or three core keywords and open the first ten to twenty results. If the truthful answer is "same features, same default look", no appeal will fix it: either build a real difference or stop. Resubmitting the same look again makes the reviewer's reading stickier, not softer.
- Change the product before the words. What reverses the verdict is a workflow or content others do not have, not the same thing described differently. A concept that is interchangeable with the top five search results stays interchangeable however you phrase it.
- Put the difference where the reviewer looks. Reviewers see three things: the first two screenshots, the first paragraph of the description, and the first screen after launch. A distinctive feature three levels deep in Settings does not exist for the review.
- Then rewrite the metadata. Replace generic praise such as "easy to use" and "powerful" with statements only your app can keep.
- Resubmit with specifics. In Resolution Center, say what is new, who it is for and what problem it solves. Resubmitting an unchanged binary gets the same verdict every time.
Appeals are for the case where the app really is different and was misread. An appeal changes one judgement; it cannot change the similarity itself.
4.2 (Minimum Functionality) is a cousin, not the same thing
A tool whose whole depth sits in one core capability can be rejected under 4.2 for having too little to do. The reviewer gets a clean device, a fresh install and a few minutes. If the value only appears with your data or after reading the manual, it reads as minimal.
Reproduce that screen yourself: clean device, fresh install, no data. Note the minute at which the app first feels useful. If it is not within the first few minutes, deepen the core path from input to result to what you can do with the result, then reply in App Store Connect in your own words about where the value first becomes visible. A reply without a fix is just a second argument, and a fix without the reproduction polishes the wrong screen.
One-minute check before you submit
Search your core concept, open the top five results, and put your first screenshot among theirs. Can a stranger tell which is yours? Can you say in one sentence what yours does that none of them do, and can that sentence be verified from the first screenshot? If not, you are at risk of 4.3 before anyone has reviewed anything. Fix it before submission, not after the rejection.
These notes are from Obelisk Club's own submissions. Apple's wording and review practice change; check the current App Review Guidelines for the exact text.