Apple Tightens App Review Rules Against Apps That 'Do Not Add Value'

Apple updated its App Store Review Guidelines this week with new language aimed squarely at apps that, in Apple's words, "do not add value to the App Store." The change lands in section 4.3(b) and tightens the existing anti-spam framework that Apple started building out last November when it cracked down on copycat apps. If you maintain apps across iOS and Android, this is the kind of policy shift worth reading carefully before your next submission, because the practical bar for getting a new app approved on the Apple side just moved.

What changed in the guidelines

The revised 4.3(b) now states that developers should not submit apps that are "indistinguishable from what's already widely available." Apple frames the reasoning around App Store health: opportunistically creating variants of existing categories or popular apps, the guideline says, degrades discovery, reduces overall quality, and harms both users and developers.

Apple then does something it rarely does, which is name names. The guideline calls out specific app types that are considered well established and will no longer be accepted as new submissions unless they offer a meaningfully different or improved experience: dating, flashlight, sound effects, wallpaper, simple timers, and fortune telling. More pointedly, Apple lists categories it now treats as inherently low value, including drinking games, Kama Sutra, fart, and burp apps. Repeated submissions of that kind, the guidelines warn, may lead to removal from the Apple Developer Program entirely.

There is also a retroactive clause that developers should not gloss over. Apple says it may remove existing apps in the established categories "going forward if they are not updated, improved, or do not attract customers." That means a flashlight or wallpaper app already live on the store is not automatically safe. Neglected apps with no user traction are now candidates for removal.

Two smaller additions accompany the main change. Guideline 1.2 picks up new language around apps with user-generated content, and guideline 4.5.3 adds restrictions on using Live Activities to send spam, phishing attempts, or unsolicited messages. The full text is available in Apple's App Store Review Guidelines.

Why Apple is doing this now

The context comes straight from this year's WWDC keynote, where Tim Cook noted that developers are submitting "well over 1,000 submissions to the App Store every hour." Cook pitched that as a sign of vitality, but the volume cuts both ways. AI-assisted development tools have dramatically lowered the barrier to shipping an app, which is good for people turning an idea into a working product and bad for a review pipeline now absorbing a flood of near-identical, low-effort software.

The numbers back up the pressure. The Information recently reported an 84% surge in new app submissions, which it suggested was straining Apple's review team. Apple pushed back on the implication that reviews are slowing down. According to an Apple spokesperson, the team processes 90% of submissions within 48 hours, and over the last 12 weeks it has handled more than 200,000 submissions per week with an average review time of 1.5 days. Apple also confirmed that while every app still gets a human reviewer, it is increasingly using AI tooling to assist that process.

Read together, the picture is clear. Apple is using AI to scale review throughput while simultaneously using policy to reduce the input volume of junk submissions. Tightening 4.3(b) is the policy half of that strategy.

Developer impact

For solo developers and small studios, the immediate effect is that "I built a clean version of an existing utility" is no longer a viable App Store pitch on its own. A well-coded flashlight app is still a flashlight app, and Apple has now said in writing that polish alone does not clear the bar. You need a defensible answer to the question of what your app does that widely available alternatives do not.

The retroactive removal language is the part that should change behavior for anyone with a back catalog. If you have older apps sitting in the named categories that you stopped updating years ago, they are now exposed. The combination of "not updated" and "do not attract customers" is the trigger. Apps with real users are comparatively safe even in crowded categories. Dormant apps with no downloads are the ones at risk.

There is a cross-platform angle here too. Google Play has run a similar quality and spam enforcement regime for years through its Spam and Minimum Functionality policy, which rejects apps that provide an unacceptable user experience, lack basic functionality, or simply repackage existing content. Developers who maintain on both stores have generally treated Google as the stricter gatekeeper on minimum functionality and Apple as the stricter gatekeeper on business model and payments. Apple's update narrows that gap. The mental model of "if it passes Google's functionality bar it'll pass Apple" is now less reliable, because Apple is asserting category-level judgment that goes beyond whether the app technically works.

What to do before your next submission

If you have something queued for either store, the practical checklist is short. Identify whether your app falls into one of the named categories, or close to one. If it does, document the meaningful differentiation in your app description and review notes rather than assuming the reviewer will infer it. Audit your existing portfolio for abandoned apps in those categories and either invest in a real update or accept that they may not survive the next sweep. And if you are using AI tooling to spin up app variants quickly, understand that the developer-account-level penalty in the new language is aimed precisely at that pattern. Repeated low-value submissions are now framed as a risk to your entire account, not just to the individual app under review.

The broader signal is that both major mobile platforms are converging on the same posture. Volume is no longer a virtue, and the stores are increasingly willing to make editorial calls about which apps deserve to exist. For developers building something genuinely distinct, that is a friendlier shelf to stand on. For anyone shipping variations on a theme, the room to do that is shrinking on both iOS and Android at the same time.