An abstract grid of feature blocks leads into an age-rating checklist and filing panel, with geometric location markers and connected dots splitting toward a final release gate.
Platform Rulesthrough The Gap a Rule Opened

Your app feature list is becoming an age-rating filing tool

Apple’s new questions on location sharing and dating or relationships create room for a small service that turns scattered app features into filing language and release checks.

Published 2026. 11. 7.

A new filing window of less than two months

Starting November 16, 2026, Apple will add “Location Sharing” and “Dating & Relationships” to its App Store age-rating questions. Every app, including existing apps, must answer both questions by January 12, 2027. There are less than two months between the appearance of the new questions and the deadline.

“Location Sharing” does not mean every feature that uses a phone’s location. It means a feature that shows a person’s real-world location to another person or group. An app that uses current location for map search and an app that lets someone send their current location to a chat contact may need different answers. The effect of location sharing on an age rating varies by country and region.

“Dating & Relationships” includes features that connect real people for dating or relationship purposes. It also includes virtual companions that exchange sexual or romantic conversations, so AI friend apps that do not call themselves dating apps also need review. Under Apple’s criteria, apps that answer yes to this feature receive a minimum age rating of 18+.

After November 16, any app submitting an update or changing its existing age-rating answers must answer the new questions first. Apps with no update planned must still complete the declaration by January 12, 2027. That makes the preparation period now through November 15, while the period most likely to see a rush of submissions runs from November 16 through January 12.

In Korea, Apple has not announced that its 18+ rating will automatically become a domestic 19+ label for every app. Games or entertainment apps may also display local ratings related to the Game Rating and Administration Committee (게임물관리위원회), the Korean game-rating body, so outcomes can differ by app type. Apple calculates ratings from developer responses, which makes a complete inventory of the app’s real features the starting point.

Turning scattered feature descriptions into a filing-ready list

Imagine an eight-person team running a local hobby-meetup app. Its operator describes it as a service for finding hiking and running groups. But the sign-up screen includes an option saying that dating is possible, the chat room has a button to send current location, and users can state relationship intentions in profiles and posts.

To answer the age-rating questions now, the operator has to search product documents, the live app, conversations with an outsourced development firm, and customer inquiries separately. They ask the developer about map features, the operations team finds the sign-up copy, and the customer team explains what kinds of relationships actually form in posts. The same details get copied among several people just to assess one feature.

The harder issue is that an app’s label and its real features may not match. Answering that there is no relationship feature based only on a name such as “Find Local Friends,” or answering that location is shared simply because the app requests location permission, can misrepresent how the product works. The questions need to be assessed against every screen and user flow in the app.

A service built for this job could walk through app screens in sequence and ask: “Who can see whose location?”, “Is it an exact current location?”, “Can users select or receive recommendations based on relationship intent?”, and “Can they have romantic conversations with a virtual character?” Each answer would attach the relevant screen and responsible person, then produce a draft response for Apple’s questions. Instead of reassembling scattered explanations, the operator reviews one feature list with evidence attached.

The same list can support user guidance and pre-release checks. If location sharing exists, check whether the screen makes the recipient, duration, and way to turn it off clear. If relationship features exist, check whether the sign-up age and app-store description conflict with the new rating. The service could also alert teams to reopen their existing answers when a future update adds location sending or relationship recommendations.

Some work does not change. An automated tool cannot make the final determination of whether a feature falls within Apple’s wording or set the Korean display rating. The service should not sell legal conclusions. It should find missed screens, preserve the evidence and revision history behind each answer, and make the final human decision easier.

Urgent demand will arise between November 16, 2026 and January 12, 2027. After that, apps will still need to answer the new items when submitting updates, and they will need to review declarations when feature changes could make earlier answers inaccurate. That turns a one-time check into a repeatable pre-release review. This policy change is a reason to move knowledge of what an app contains out of an operator’s memory and into a manageable workflow.

How earlier movers handle it

Google Play has developers answer content questions and then assigns regional ratings using International Age Rating Coalition criteria. Issuing a rating is free for developers, and the questions must be resubmitted when app content changes. Apps with no rating or inaccurate answers can be removed or suspended.

This shows why simply completing a questionnaire once is unlikely to be a durable service. The useful layer is where teams continuously record app changes, identify features that differ from earlier answers, and preserve filing evidence. Apple’s change creates the same operational problem.

On Steam in Germany, games without a valid age rating have not been shown to local customers since November 15, 2024. Developers can complete Steam’s content questionnaire to receive a self-rating or connect a rating from a German self-regulatory body. People who already bought the game can continue to use it, but new customers cannot discover or buy an unrated game.

The cost of completing the separate questionnaire has not been disclosed, but developers who want to avoid an interruption in sales now have deadlines and submission status to manage. A publisher responsible for several games needs one place to see which games have completed their answers and which screens support them. The same type of dashboard can work for a company operating several Apple apps or an app production agency.

Instagram Teen Accounts show how age categories can become real product settings. Accounts for people aged 13 to 17 receive private accounts, limits on messages from strangers, sensitive-content restrictions, and nighttime notification limits by default. People under 16 cannot loosen some settings without parental approval.

Meta introduced Teen Accounts in India in stages, and they are now operated globally. Meta said there were at least 54 million active Teen Accounts by April 2025. It also said that 97% of users aged 13 to 15 kept the default protection settings. These are Meta’s own reported figures. They show why a service may need to review actual screens and default settings, not only rating declarations.

Four things to build now

1. A 30-minute app feature reading service

  • What it does: Reviews sign-up, profile, map, post, and chat screens with the operator, then creates draft answers to the two new questions and screen-based evidence.
  • Who uses it: A three-person operator of a local meetup app that relies on an outsourced vendor rather than an in-house developer.
  • Why now: The questions appear on November 16, but apps without a prepared feature list will need to move at once before January 12.
  • First screen: After entering the app name and launch country, the user sees a start-review button that says, “Upload your screens in order, from sign-up through location sharing.”

2. A pre-update declaration-change alert

  • What it does: Compares descriptions and screens for newly launched features with earlier records, then flags areas where age-rating answers may need review.
  • Who uses it: An AI friend app operator that changes features several times a month but has only one person responsible for releases.
  • Why now: Romantic virtual companions also fall within the new relationship item, so the operator needs to check whether earlier answers still fit whenever the conversation style changes.
  • First screen: A field for pasting “features added or removed in this update” appears beside a list of “items that may differ from your existing declaration.”

3. A deadline dashboard for app production agencies

  • What it does: Tracks the responsible person, response status, evidence screens, and planned submission date for each client app.
  • Who uses it: A small app production agency managing around ten client apps across maps, communities, and dating.
  • Why now: The same January 12 deadline applies to every app, concentrating requests for client materials and answer approvals at the same time.
  • First screen: Each app is marked “feature review not started,” “awaiting client confirmation,” or “ready to submit,” and ordered by approaching deadline.

4. An 18+ transition-preparation bundle

  • What it does: Reviews the sign-up age, app description, user guidance, and reporting and blocking screens as one flow for an app that decides to retain relationship features.
  • Who uses it: An operator of a Korean-language AI companion app that started with friend chats and added a paid virtual-partner feature.
  • Why now: Rather than hiding the feature or only changing its name, the app needs to align screens and operating rules with a minimum 18+ rating.
  • First screen: The operator chooses either “keep relationship features” or “consider removing features,” then sees the screens that need changes for that choice.

Why this matters where you are

Check whether your app store or local rating system asks developers to re-submit age-rating information when content changes. The specific rating labels and local rules may differ, but the underlying work is the same: identify what users can actually do in the product and retain evidence for each answer. A reusable feature inventory can make that work part of every release review.

What to review in 30 minutes today

Open one live app and record the screens yourself, from sign-up through profile, map, posts, and chat. While watching the recording, mark every moment when another person can see a real-world location and every moment when relationship intent appears. If you cannot answer the two questions and immediately find the supporting screen without asking an outsourced developer, it is worth testing a service that builds that feature list for you.

Sources

6 sources

Every fact in this article came from the pages below. Check them yourself.

Your app feature list is becoming an age-rating filing tool | Prometheon