Apple Is About to Let Parents Cap Your App by Category. In July, Your Age Rating Decides Whether Your Retention Survives Screen Time.
Apple Is About to Let Parents Cap Your App by Category. In July, Your Age Rating Decides Whether Your Retention Survives Screen Time.
At WWDC 2026 on June 8, buried under the App Store commerce headlines, Apple said it's reworking the age-rating questionnaire starting in July. Every developer will have to classify their app into one of four buckets (Social Media, Entertainment, Games, or Other), and parents will be able to set daily time allowances per category in Screen Time, instead of approving or blocking apps one at a time.
If you ship anything on iOS that lives or dies on daily minutes, that's the line that matters. Your category just became a growth variable. And you don't fully control which bucket you land in.
What actually changed
The old Screen Time model was per-app. A parent picked your app, set a limit or a block, done. It was annoying for parents to manage and easy for kids to route around, so most families used the blunt instruments: total downtime, app-by-app blocks on the obvious offenders.
The new model is per-category. Apple makes you self-classify during App Store Connect submission, surfaces that category to the OS, and lets a parent say "90 minutes of Entertainment a day across everything" or "30 minutes of Social Media." Your app no longer competes for an exception. It competes for a shared, capped pool of minutes with every other app in its bucket.
That's the part worth sitting with. Before, the ceiling on your usage was attention and habit. Now, for any device with Screen Time limits set, there's a literal hard ceiling on your category, and you're splitting it with competitors.
Why this is a distribution story, not a parental-controls story
Most of the coverage framed this as a kids-and-screens feature. For a solo operator it reads differently. Three things change.
First, the ceiling is now shared and finite. If you built a meditation app, a habit tracker, or a kids' learning app, your daily engagement used to be capped only by how good your retention loop was. If a meaningful share of your users are on managed devices, your category's daily allowance is now an upper bound you can't engineer past. You can have the best retention loop in your category and still lose minutes to whatever else sits in the same bucket.
Second, classification is consequential and fuzzy. Is a journaling app with a social feed "Social Media" or "Other"? Is a language-learning app with leaderboards and streaks "Education"-flavored "Other," or does the game layer push it toward "Games"? Apple writes the questionnaire and Apple's reviewers get the final say. The difference between "Other" and "Social Media" could be the difference between an uncapped app and one that gets throttled by default on every managed device.
Third, "Social Media" is becoming a penalty box. The regulatory and parental pressure of the last two years has pointed in one direction: social media is the category everyone wants to limit. If your app gets swept into that bucket because it has a feed and comments, you inherit the suspicion aimed at the platforms, without any of their scale to absorb it.
The misclassification trap
Here's where it gets uncomfortable for the people reading this. A lot of indie apps are deliberately category-ambiguous because that ambiguity is the product. The fitness app that's really a social accountability app. The reading app that's really a community. The "productivity" tool with a dopamine feed bolted on because engagement metrics looked good in the deck.
That design choice was free when Screen Time was per-app. It now has a cost. The more your app borrows mechanics from social media to juice engagement, the more likely it gets classified (by the questionnaire or by a reviewer) as the thing parents are actively trying to cap.
I don't have a clean answer for the genuinely mixed-use app, and I'm not going to pretend I do. But the strategic question is now concrete: which bucket do you want to be in, and is your feature set arguing for that bucket or against it?
What I'd actually do
If you ship a consumer iOS app, do three things before the July change lands.
Pull up your app and decide, honestly, which of the four categories Apple is going to put you in, not which one you'd prefer. Look at your actual feature set the way a reviewer filling out a questionnaire would. If you have a feed, comments, profiles, and follows, assume "Social Media" is on the table whether you like it or not.
Then check how exposed you are. If a real slice of your users are minors or on family-managed devices, the category cap is a direct hit to your DAU ceiling and you should model it. If your users are adults who never touch Screen Time limits, this is mostly noise for you: say so to yourself and move on instead of panicking.
Finally, if you're on the bubble between "Social Media" and "Other," weigh whether the engagement mechanics that put you there are actually earning their keep. A feed that adds 5% to session length but reclassifies your whole app into the capped bucket is a bad trade. This is the rare case where removing a growth feature might protect growth.
The honest counter-take: this may amount to very little for most indie apps. Plenty of people set up Screen Time once, hit the friction, and never touch the category limits. Adoption of the new per-category controls could be low enough that the practical impact rounds to zero, and I could be overweighting a feature that looks scary in a keynote and gets ignored in the wild. If your users skew adult and unmanaged, that's probably exactly what happens.
But the cost of checking is an afternoon, and the failure mode (waking up to find your app sorted into the one category parents are told to limit) is the kind of platform decision you want to see coming. On iOS, the platform always gets the last word on distribution. This is just a new place it gets to use it.
Author
Lukas
@lukcombinator