Apple updated the App Review Guidelines: three rules to re-read

· 6 min read

#apple-ecosystem

Apple revised the App Review Guidelines on October 16. The headline is about "nudification" apps and bait-and-switch tactics, but three of the changes apply to ordinary indie apps, including mine, and are worth ten minutes of your time before your next submission.

What changed

Apple's own change list is short. The items that matter for most developers:

In the companion post Apple also says it blocked over 150K apps with safety issues and terminated over 193K developer accounts for fraud and abuse last year. That is the context: the update is aimed at coordinated fraud, not at you. The wording still binds everyone.

Three changed guidelines and what to check for each Three rows. Guideline 2.5.19 on hidden features leads to listing flag-gated features in Notes for Review. Guideline 2.3.14 on creative assets leads to no prices or discounts and all-ages content. Guideline 1.2 on AI content creation apps leads to a filter, reporting, blocking and contact information. Changed guideline Check before you submit 2.5.19 hidden or dormant features List flagged features in Notes for Review 2.3.14 creative assets No prices or discounts all-ages content 1.2 AI content creation apps Filter, report, block plus published contact info
Each changed guideline on the left, the check it adds to your next submission on the right.

2.5.19: dormant features and your feature flags

The new text reads: "Don't include any hidden, dormant, or undocumented features in your app; your app's functionality should be clear to end users and App Review." Hiding undocumented features in the binary, for example through code obfuscation, is grounds for removal and account termination.

The companion post is more specific about the target: apps that misrepresent what they do during review and then change after approval, "for example, adding features or functionality that weren't included in the version of the app that was submitted to App Review."

Here is my reading, and this part is inference, not Apple's words. A remote feature flag by itself is not what Apple is describing. The pattern they describe is code that is dark during review and wakes up afterwards, with reviewers never seeing what it does. The safe side of the line is the one 2.3.1(a) has always asked for: describe new functionality with specificity in Notes for Review and make it accessible to the reviewer. So, before you submit:

I do ship features behind remote flags in my apps, and until now I never mentioned them in Notes for Review. From my next submission on, every flag-gated feature goes into the notes, with a way for the reviewer to turn it on.

2.3.14: the new creative assets now have a rule

On October 5 Apple introduced creative assets: image and video assets for the product page header and for search results, managed through a new Asset Library in App Store Connect, with a preview tool that shows how they render in Dark Mode and on different devices. Eleven days later they got their own guideline.

2.3.14 says creative assets "must pertain to your app's content and functionality or overarching brand, follow standard metadata guidelines, and be appropriate for all audiences." They must not include inappropriate content, references to other apps with an intent to mislead, unverifiable product claims, or specific or discounted pricing information.

Two practical consequences. First, a header that says "50% off this week" is out, even though a seasonal campaign is exactly what Apple suggests these assets are for. Promote the season, not the price. Second, "appropriate for all audiences" applies regardless of your app's age rating, so a 17+ game still needs an all-ages header. Apple's asset best practices page has templates and more detail; read it before you brief a designer.

1.2: AI content creation apps are now named

Guideline 1.2 has always required four things from apps with user-generated content: a filter for objectionable material, a way to report content with timely responses, the ability to block abusive users, and published contact information. The scope line now reads: "This includes social media, user-generated content platforms, and AI content creation apps."

The new paragraph adds teeth. Developers "who fail to implement appropriate safeguards or fail to remediate identified violations after notice may be considered in violation of the Developer Code of Conduct." Apple's process is: ask you to remove the content and provide a compliance plan, possibly remove the app until you do, and remove repeat offenders from the Developer Program.

If your app lets users generate images or text with an AI model and share them with other users, you are now clearly inside 1.2. If generation is private to the user and nothing is shared, the guideline text does not obviously apply, but that is my inference and Apple has not said so. An in-app way to report a bad output and a contact address cost little and remove the question.

In HealthBar, Master Ronnie's chat generates text, but nothing is shared between users, so I treat it as outside 1.2. The app has no way to report an AI reply yet, and after this update adding one is on my list.

The ten-minute check

  1. Open your Notes for Review template. Does it list every flag-gated or server-enabled feature in the build, and how the reviewer can reach it?
  2. Grep your release build for debug menus, hidden gestures and test-only screens.
  3. If you have uploaded creative assets, check them against 2.3.14: no prices, no discounts, no unverifiable claims, all-ages content.
  4. If users can generate or share content, confirm the four 1.2 requirements exist in the app, not only on your website.

Translations of the new guidelines arrive within a month. The English text is live now, and it is the one App Review uses.

Sources