Guide · 7 min read
Apple Low-Quality App Removal: What the June 2026 Guidelines Mean for Indie Devs
Apple updated its App Store Review Guidelines on June 8, 2026 — released at WWDC — with language that goes beyond blocking new submissions to actively removing apps already on the store. The change targets two classes of apps: low-effort apps in oversaturated categories, and any app that fails to attract users or hasn't been updated. If your app is in dating, flashlight, sound effects, wallpaper, timer, or fortune-telling categories, or if it has gone months without an update and few downloads to show for it, the risk is now explicit and official.
Guideline 4.3(b): the exact change that puts existing apps at risk
The June 2026 update revised guideline 4.3(b) — historically a spam rule — to target low-quality and stale apps explicitly. Previous versions of 4.3 focused on blocking new submissions of copycat or template-generated apps. The 2026 revision added a removal trigger: Apple may now remove existing apps if they are not updated, improved, or do not attract customers. That sentence is new, and it shifts the policy from reactive (review rejection) to proactive (store removal).
Two tiers are named in the updated text. The first tier covers well-established categories — Apple's published list includes dating apps, flashlight utilities, sound effect boards, wallpaper apps, simple timers, and fortune-telling apps. These categories are now treated as saturated enough that new submissions face higher scrutiny and existing apps must demonstrate ongoing relevance. The second tier applies to what Apple describes as low-effort experiences: drinking games, off-color content, and similarly thin apps. Developers who repeatedly submit these face removal from the Apple Developer Program entirely — not just store delisting.
The change is significant because it applies retroactively to apps already on the store. Previously, once an app passed review it remained unless it violated a rule through an update. The new language creates a continuous compliance obligation: your app must stay updated and must attract users. Vague as those criteria are, the policy is now written.
The 6 oversaturated categories named in Apple's guidelines
Apple's updated guidelines name six specific category types where new submissions face limits and existing apps face removal risk: dating apps, flashlight apps, sound effects apps, wallpaper apps, simple timer apps, and fortune-telling apps. If your app falls into any of these categories and has not been updated since 2024, it is at explicit risk. New submissions in these categories require a demonstrably different or improved experience to pass review — "yet another timer app" is now an actionable rejection reason, not just an editorial preference.
The reasoning Apple gives is market saturation: these categories are crowded with functionally identical apps, and Apple's CEO has noted that developers submit over 1,000 apps per hour. The AI-assisted wave of low-effort app generation accelerated the problem Apple is now correcting for. If your app is in one of these six categories and offers a meaningfully differentiated feature — a timer that integrates with Health Kit, a wallpaper app with AI-generation, a dating app for a specific community — document that differentiation explicitly in your App Store description and What's New field. Reviewers are specifically looking for it now.
If your app falls into these categories but isn't particularly differentiated, a metadata audit is the starting point. The ASO metadata quarterly audit guide covers exactly what to update to demonstrate active maintenance — even if the underlying app hasn't changed, updated screenshots, a revised description, and a What's New entry signal ongoing investment. Apple's review process weighs these signals.
What 'fails to attract users' means in practice
Apple has not published a numeric download threshold or engagement benchmark that defines 'failing to attract users' — the criterion is deliberately vague. What Apple has confirmed through its App Store Improvements process is that apps receive notice when they are identified as out of date or not being downloaded. The combination of both signals — no updates AND low downloads — appears to be the trigger, rather than either one alone.
The practical interpretation, based on how the App Store Improvements notice has been applied historically: an app that hasn't been updated since 2023 or earlier with a very low monthly download count is at risk. An app with low downloads but regular updates is less exposed. An app with solid downloads but no updates since 2022 is moderately exposed, particularly in the named saturated categories. The system prioritizes removal of apps that appear abandoned, not apps that are simply niche.
What this means operationally: if you have dormant apps on your account that you haven't touched in years — side projects, experiments, one-off launches that never gained traction — the calculus has changed. Letting an app sit as a passive listing with no maintenance is no longer risk-free. Either update it, submit a metadata-only update to show activity, or voluntarily remove it before Apple contacts you. A voluntary removal preserves your developer reputation; a forced removal creates a record.
How Apple's App Store Improvements process works before removal
Apple does not remove apps without notice. The App Store Improvements process sends an email to the developer's account address notifying them that an app is at risk of removal due to being out of date or not being downloaded. The notice gives developers a window to submit an update — Apple has historically given 30 days, though the exact window may vary. If no update is submitted, the app is removed from the store. Users who already have the app installed keep their copy, and existing in-app purchases remain accessible. The app is no longer searchable or downloadable by new users.
The reinstatement path exists: an app removed through this process can return to the store once an update is approved. But the removal itself is visible to anyone searching for your app — they simply won't find it. For apps with ongoing users, this is disruptive enough to treat as an urgent maintenance obligation. For truly abandoned apps, the removal window gives you a final decision point: invest in an update, or let the app go.
The notice email goes to the address on your Apple Developer account, which may not be one you monitor closely if the app is a side project. Check your developer account's primary email address now if you have inactive apps in your portfolio. A notice sitting unread in a filtered folder can expire while you miss the remediation window. If you're unsure whether any of your apps have received a notice, log into App Store Connect — flagged apps appear in the App Status column with a specific notice indicator.
The 5-point audit to protect your app before Apple contacts you
Run this audit on every app in your portfolio, prioritizing any app that hasn't been updated in 12 or more months and any app in the six named saturated categories.
1. Check your last update date. Apps Store Connect shows the date of your most recent approved update. If it's older than 12 months, you're in the risk zone. A metadata-only update — new screenshots, a revised description, or even a corrected typo — counts as an update and resets the clock. Use the screenshot editor to refresh your screenshots to current device sizes if they haven't been updated since iOS 26. Updated App Store screenshot sizes are required for the latest devices, and mismatched sizes are both a quality signal and a user experience failure.
2. Review your download trend. App Store Connect Analytics shows installs by time period. If your monthly installs are in the single digits and declining, that's the 'not attracting users' signal Apple is watching. A paid Apple Search Ads campaign — even a minimal one at a few dollars per day — reactivates install velocity. 3. Audit your category fit. If your app is in one of the six named saturated categories, make sure your description, What's New field, and App Store subtitle all make the case for differentiation. Reviewers are specifically checking these fields now. See the subtitle vs promotional text guide for how to use those 30 characters to communicate differentiation efficiently.
4. Update your screenshots and icon. Screenshots and icons that haven't been updated for iOS 26 read as abandoned, both to Apple's review process and to users. A single updated screenshot set signals active maintenance and typically improves conversion. Current app icon size requirements include dark and tinted variants for iOS 26 — supplying these signals that the developer is paying attention. 5. File a maintenance update. Even if you change nothing in the code, a build submission with an updated description or updated assets counts as an active update. Apple's Improvements process appears to weigh submission activity, not just crash rates or ratings — showing that a developer is present reduces risk.
If you're in a flagged category: what a 'meaningfully different experience' actually requires
Apple's guidelines say apps in saturated categories won't be accepted 'unless they offer a meaningfully different or improved experience.' That phrase is doing a lot of work — here's what it means in practice based on what App Store reviewers have historically passed versus rejected in these categories.
For timer apps: a timer alone fails. A timer with Health Kit integration, a timer paired with a specific workflow (Pomodoro tracker with stats, interval training timer, medication reminder with scheduling) or a timer with significantly improved UX for a specific user group (accessibility-focused, kitchen-specific, workout-specific) passes. The key is a named, specific use case that doesn't already have ten nearly identical apps. For wallpaper apps: a gallery of static wallpapers from a stock API fails. AI generation, an artist collaboration with unique licensed content, Live Photo or dynamic wallpaper creation, or a community-upload model with curation all qualify. The differentiation needs to be in the core function, not in the marketing copy.
Across all flagged categories, the audit question is the same: could Apple's reviewer download the top 10 apps in this category and find yours indistinguishable in core function? If yes, the app needs either a meaningful feature addition or a pivot in positioning that makes its differentiated use case explicit in the first 200 characters of the description. The App Store description framework covers how to structure those first three visible lines — the ones that show without 'more' being tapped — to lead with the thing that makes your app different rather than what it shares with everything else in the category. Use the compare tool to benchmark your listing against the top apps in your category and identify where the description falls short.
Audit your portfolio before Apple does
The June 2026 guideline update is Apple's most explicit signal that the App Store is moving from open archive to curated marketplace. The apps that survive that transition are the ones that show clear activity — regular updates, maintained screenshots, current device support — and clear differentiation from the category they compete in.
The audit above takes an afternoon. Refreshing screenshots in the editor takes less. Both cost far less than the alternatives: a removal notice with a 30-day deadline, or an app that disappears from search for new users while you're not watching.
Refresh your screenshots in the editor →
Frequently asked questions
which app categories does apple target for removal in 2026
Apple's updated guideline 4.3(b) explicitly names six category types at elevated removal risk: dating apps, flashlight apps, sound effects apps, wallpaper apps, simple timer apps, and fortune-telling apps. Apps in these categories that haven't been updated or are not attracting downloads may receive a removal notice. Low-effort apps in categories like drinking games and crude humor face the additional risk of removal from the Apple Developer Program, not just store delisting.
how much notice does apple give before removing an app
Apple's App Store Improvements process emails the developer account holder before removing an app. The notice gives developers a window to submit an update — historically 30 days — before removal takes effect. Apps that crash on launch are removed immediately without notice. After removal, the developer can submit an updated build for review; if approved, the app returns to the store.
does a metadata-only update count for apple app store improvements
Yes. A metadata-only update — updated screenshots, a revised description, a new What's New entry, or even a minor copy correction — counts as an active update submission. It resets the 'last updated' signal Apple evaluates for App Store Improvements notices. If your app's code is stable and doesn't need changes, a metadata refresh is the lowest-effort way to demonstrate ongoing maintenance and reduce removal risk.
what does apple mean by an app that does not attract users
Apple hasn't published a specific download threshold. The signal appears to be the combination of low installs and no recent updates — an app that is both stagnant and uninteresting to users. An app with very low downloads but regular updates is less exposed than one with low downloads and no updates since 2022 or earlier. The practical takeaway: apps that show no download activity and no developer activity are the priority target. Either active marketing, a metadata refresh, or a small paid UA campaign (even minimal Apple Search Ads spend) reactivates both signals.
can an app removed for low quality come back to the app store
Yes, with an important distinction depending on why it was removed. Apps removed through the App Store Improvements process (outdated, low downloads) can return once a new build is approved — the developer submits an update, it passes review, and the app is relisted. Apps removed because they fall into the low-effort/mediocre category under 4.3(b) face a higher bar: the update needs to demonstrate a meaningfully different experience, not just a build bump. Apps whose developers face repeated low-quality submissions risk removal from the Apple Developer Program entirely, which is not reversible through a single app update.