App Store Guideline 4.3(a) 設計垃圾應用：回覆、申訴還是重建

First published on tychelabs.net.

Rejected under guideline 4.3 as spam or a copycat? Here is what 4.3(a) and 4.3(b) actually say, and the seven questions that decide whether to reply, appeal or rebuild.

Guideline 4.3 is the rejection that feels most personal. Other rejections say your app has a bug or a missing link. This one says your app should not exist in its current form, because the App Store already has enough like it. It is also one of the hardest to respond to well, because the right move depends on which half of the guideline you were rejected under and on how different your app really is.

We have not been rejected under 4.3 ourselves, so this guide does not have a war story. What it has is the exact text of the guideline, the questions we ask before deciding whether a client should reply, appeal or rebuild, and a description of how we positioned our own app so that the question would not come up.

What guideline 4.3 says

The guideline has two parts, and Apple cites them separately.

4.3(a) says: "Don't create multiple Bundle IDs of the same app (for example, submitting a separate map app for every city in the world instead of a single worldwide map that allows users to search any city). This practice results in unnecessary apps, which makes it hard for users to find the apps they want. If your app has different versions for specific locations, sports teams, universities, etc., consider submitting a single app and providing the variations using in-app purchase" [1].

4.3(b) says: "Don't submit apps that are indistinguishable from what's already widely available. Opportunistically creating variants of existing app categories or popular apps degrades App Store discovery, reduces overall app quality, and harms both users and developers." It names categories Apple considers "well established", including dating, flashlight, sound effects, wallpaper, simple timers and fortune telling, and says Apple "will not accept new submissions unless they offer a meaningfully different or improved experience". It also lists kinds of apps Apple considers low effort, and warns that "repeated submissions of this kind may lead to removal from the Apple Developer Program" [1].

Two neighbouring guidelines are often cited alongside 4.3. 4.2.6 says that "apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content" [1]. 4.1 Copycats says: "Don't simply copy the latest popular app on the App Store, or make some minor changes to another app's name or UI and pass it off as your own" [1].

If this is you right now: App Store rescue, from £650. Write before 2pm UK time, Monday to Friday, and we reply the same working day.

Why you were rejected: three different situations

Before deciding what to do, work out which of these describes your app. The right response is different for each.

Situation 1: you publish several apps that share a codebase

This is the classic 4.3(a) case. A gym chain with one app per branch. A publisher with one app per magazine. A white-label agency shipping the same app for each client under the client's name. Apple's view is that these should be one app with the variation inside it, chosen by the person or sold through in-app purchase [1].

There is a legitimate version of this, and Apple describes it in 4.2.6: the template provider ships "a single binary to host all client content in an aggregated or 'picker' model", such as a restaurant finder with a page for each restaurant [1]. There is also a route where the client submits the app from their own developer account, as the provider of the content, rather than the agency submitting on their behalf [1].

Situation 2: your app is in a crowded category and the reviewer could not tell it apart

This is 4.3(b). The app is yours, built from scratch, but to a reviewer spending a few minutes with it, it looks like the twenty apps above it in search results. Apple names some categories, but the list is illustrative. Timers, note-takers, habit trackers, QR scanners, white-noise apps, calculators and simple photo filters all get this treatment.

Situation 3: your app looks like a specific popular app

If the icon, name, screens or flow closely resemble one well-known app, you may be cited under 4.1 Copycats as well as, or instead of, 4.3. Apple treats impersonation as a conduct issue "and may result in removal from the Apple Developer Program" [1], so this situation is the most serious.

Respond, appeal or rebuild: how we decide

There are three possible moves after a 4.3 rejection, and they are not interchangeable.

Respond means replying to the reviewer in App Store Connect with information they may not have had. It costs a day or two and works when the reviewer could not see what makes the app different.

Appeal means asking the App Review Board to overrule the rejection. Apple asks you to "provide specific reasons why you believe your app complies with the App Review Guidelines", to submit only one appeal per rejected submission, and to respond to any requests for information before appealing [2]. An appeal is for when you believe Apple is wrong, not for when you hope a second reviewer will be kinder.

Rebuild means changing the app, or your portfolio of apps, so that the objection no longer applies. It costs the most and is the only move that works when the reviewer is right.

Here are the questions we ask.

Which clause is cited, 4.3(a) or 4.3(b)? If it is (a), you have a portfolio problem and no amount of explaining one app will fix it. If it is (b), the question is whether the difference is real and whether a reviewer can see it.
Can you state the difference in one sentence that a non-user would understand? "Our timer uses a nicer colour scheme" is not a difference. "Our timer reads the recipe aloud and pauses when you leave the kitchen" might be. If you cannot write the sentence, you have your answer: rebuild.
Is the difference visible in the first two minutes? Reviewers are quick. If the distinctive feature is behind sign-up, a paywall, a settings toggle or a third screen, the reviewer may never have reached it. That is a case for responding, with a demo video and review notes that point straight at it, before you consider an appeal.
Does your listing make the same case? Compare your name, subtitle, screenshots and first paragraph with the three apps you most resemble. If they are interchangeable, fix the listing as part of your response. Apple's reviewers see the listing as well as the build, and metadata must "accurately reflect the app's core experience" [1].
Are there other apps on your account that look like this one? If so, assume the reviewer has seen them. Consolidating them, or removing the ones that no longer matter, is often what gets the main app through.
Did you build it from a template, app builder or purchased source code? If yes, 4.2.6 is in play even if only 4.3 was cited. Reskinning does not solve it. Either the content owner submits from their own account, or the app has to become something the template did not provide.
Would you be comfortable showing the reviewer your app and the app it resembles side by side? If the honest answer is no, do not appeal.

In short: respond when the reviewer missed something that is already there; appeal when the app clearly complies and the rejection is a mistake; rebuild when the reviewer is right.

How to respond well

If you decide to respond, do it properly.

Reply in the rejection thread, not in a new submission. The reviewer who rejected you, or their team, reads the reply. Keep it short and specific.
Lead with the one-sentence difference. Then list two or three concrete features that no comparable app has, and say exactly where to find each one in the app.
Attach a short screen recording. Apple suggests being ready with a demo video when features are hard to reach or reproduce [2]. Thirty to sixty seconds that go straight to the distinctive feature is enough.
Fix the listing at the same time. Put the difference in the subtitle and the first screenshot. If the reviewer's objection was that the app looks generic, make it stop looking generic before they look again.
If you also have duplicate apps, say what you are doing about them. "We have removed the three regional versions from sale and this app now covers all regions" is a sentence reviewers respond to.
Then resubmit. A reply alone does not restart review. Resubmit the build, with changes if you made any.

How to appeal, if the app really complies

Appeals are read by the App Review Board, not by the original reviewer. Apple's conditions are specific reasons, one appeal per rejected submission, and no outstanding information requests [2]. Write the appeal as an argument, not a complaint:

Quote the guideline as cited.
State what the app does that places it outside the guideline, with reference to specific screens.
Name the apps you believe the reviewer compared you with, and say in one line each how yours differs.
Attach the same recording you would attach to a response.

Expect an appeal to take longer than a resubmission. Keep working on the listing while you wait.

How to rebuild so the objection goes away

If the reviewer was right, a rebuild does not have to mean starting over. It means finding the one thing your app does, or could do, that the category does not.

We went through this exercise with Cuefold, our own teleprompter camera app, before writing any code. Teleprompter apps are a crowded category. When we researched it in October 2026, we found that the features we had sketched already existed: voice-controlled scrolling was another app's core product, recording line by line with automatic stitching existed, and showing the script on the outer screen of a folding phone was something any competitor could ship quickly. A plain teleprompter camera would have been a weaker copy of apps already on the store.

So we built the app around something we did not find anywhere else. In Cuefold you read the whole script in one take, and when you stumble you simply say the sentence again without stopping. The app knows the script, aligns your speech to it on the device, and assembles the last good read of every line into a clean video. We call it Clean Cut, it is the first thing the app's store description talks about, and it is reachable in the first minute. Cuefold is on the App Store and was never questioned under 4.3.

The general lesson is the one Apple states in 4.2: an app should "include features, content, and UI that elevate it beyond a repackaged website" [1]. For a 4.3 rebuild, that means:

Pick one capability the category lacks and make it the headline. Not three small improvements; one thing someone would switch apps for.
Put it in the first session. No sign-up, no paywall, no settings toggle between the person and the feature.
Say it in the name, subtitle and first screenshot. The listing is where the reviewer forms their first impression.
Consolidate your portfolio. If you have several near-identical apps, one strong app with in-app variations is both the compliant route and usually the better product.
Drop the template look. If the app was built from a template or app builder, the navigation, icon set and layouts will say so. Change what the person sees first.

When not to bother

Sometimes the honest answer is that the app is a hobby project in a category Apple has said it is no longer accepting new entries to without a meaningful difference. If you cannot name the difference, and are not willing to build one, a 4.3 rejection is Apple telling you so. Spending weeks on appeals will not change the outcome, and repeated submissions of the same app can put your developer account at risk [1].

If the app was built for you by someone who has since moved on, and you are not sure which situation you are in, we can take over the app, read the code and the rejection, and tell you plainly whether a response, an appeal or a rebuild is the right call.

Checklist before you reply to a 4.3 rejection

You know whether (a), (b), 4.2.6 or 4.1 was cited, and which situation above you are in.
You can state the app's difference in one sentence.
That difference is reachable in the first two minutes without sign-up or payment.
The name, subtitle and first screenshot make the same claim.
Any near-duplicate apps on your account have been consolidated or removed, and your reply says so.
You have a 30 to 60 second recording that goes straight to the distinctive feature.
You have decided, honestly, between responding, appealing and rebuilding, and are not appealing simply because you disagree.

Questions we get asked

What is the difference between guideline 4.3(a) and 4.3(b)?

4.3(a) is about publishing several apps that are really one app, for example a separate bundle ID for each city, team or client. Apple wants one app with the variations inside it. 4.3(b) is about submitting an app that is indistinguishable from what is already widely available in its category. The first is a portfolio problem; the second is a differentiation problem.

Should we appeal a 4.3 rejection?

Only if the app clearly offers something the comparable apps do not and the reviewer appears not to have seen it. Apple asks for specific reasons why the app complies, one appeal per rejected submission, and answers to any outstanding information requests first. If you cannot state the difference in one sentence, a rebuild is the better use of the time.

Our app was built from a template. Can we still get it approved?

Guideline 4.2.6 says apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content. So the content owner submitting from their own account can help, but the app also has to offer something beyond the template. A reskin alone rarely gets through.

Can one rejected 4.3 app put our other apps at risk?

Apple says repeated low-effort submissions may lead to removal from the Apple Developer Program, and reviewers can see the other apps on your account. If you have several near-identical apps, consolidate them before resubmitting rather than after.

How long does a 4.3 appeal take?

Apple does not publish appeal times. In our experience, replying to the reviewer and resubmitting is faster than an appeal, so if you can improve the listing or make the distinctive feature easier to find, do that first and keep the appeal for cases where the app clearly complies.

Rejected under 4.3 and not sure whether to reply, appeal or rebuild? Our App Store launch and rejection rescue starts at £650 and takes 2 working days. We read the rejection against the guideline, compare your app and listing with the apps a reviewer would compare it to, and give you a straight recommendation with the reply or the rebuild plan to go with it. Send us the rejection message and a link to the app.

What to do next

Free: run your rejection message through our App Store rejection decoder.
Talk it through: book a 20-minute call and we will tell you honestly whether we are the right people to help.
Fixed price: App Store launch and rejection rescue, from £650, two working days, ending in a fix plan or the fixes made.

Sources

Apple Developer, "App Review Guidelines" (4.1, 4.2, 4.2.6, 4.3, 2.3): https://developer.apple.com/app-store/review/guidelines/
Apple Developer, "App Review" (appeals, demo videos, expedited review): https://developer.apple.com/distribute/app-review/