Apple's new bait-and-switch rule 2.5.19: what it means for AI-built and fast-shipped apps

On 16 October 2026 Apple updated its App Review Guidelines: apps that change after approval can be removed from the App Store and the Developer Program, and AI-generated intimate imagery is now explicitly covered. Here is what founders commissioning an iOS app should check.

On 16 October 2026 Apple published updated App Review Guidelines and a second note strengthening them against two things: nonconsensual intimate imagery, and “bait-and-switch” apps. Both matter to anyone commissioning an iOS app, and the second is easy to trip over by accident.

What Apple says changed

Translations of the guidelines follow within a month. Apple did not give a separate effective date; the guidelines are live as published.

Why this catches fast-moving teams

Teams that ship quickly, particularly with AI coding tools, often switch features on after launch: a remote-config flag, a server-side toggle, a new AI feature behind a login. If that feature was not in the build Apple reviewed, it is exactly what 2.5.19 describes. The penalty is not a rejected update. It is losing the developer account.

So what

Ask your supplier three things. Is everything the app can do disclosed in the review submission, including features that are switched off today? If the app lets users generate or upload images or text, what moderation and reporting is built in? And who owns the Apple Developer account, you or them? That last one decides who carries the risk if the account is ever threatened.

We build and submit iOS and Android apps with the release notes and review disclosures treated as part of the product, not an afterthought. If you are planning an app and want it to clear review first time, start a project.

← All research

More research.

GitHub's Copilot metrics now count OpenCode and Claude Code traffic: who really uses which AI coding tool

On 23 October 2026 GitHub added a per-tool breakdown to the Copilot usage metrics API, so tools such as OpenCode and Claude Code are counted even without editor telemetry. It shows how mixed the AI coding tool stack inside software teams has become.

Read ›

GitHub Copilot retires Claude Opus 5 and GPT-5.6 Terra on 16 November: the model-churn bill for buyers

GitHub has announced that Claude Opus 4.8, Claude Opus 5 and GPT-5.6 Terra leave every Copilot experience on 16 November 2026. For anyone commissioning AI-assisted development, model retirement is now a monthly event to plan around.

Read ›

GitHub Copilot now benchmarks how 'agent-first' your developers are against your industry

On 22 October 2026 GitHub added opt-in industry comparisons to its Copilot impact dashboard, ranking firms by share of agent-first developers and by the merge rate of agentic pull requests. Here is how to read the numbers when you are buying software.

Read ›

GitHub Copilot agentic autofix is generally available: AI now fixes security alerts, and bills for it

GitHub made agentic autofix for code scanning alerts generally available on 15 October 2026. Copilot can now fix up to 25 security alerts in one pull request, using AI credits your supplier or your team pays for.

Read ›

GitHub AI Scan for pull requests goes GA: AI security checks for PHP, Terraform and Dockerfiles

GitHub's AI Scan for pull requests became generally available on 15 October 2026, checking languages the standard scanner misses. Findings are advisory and cannot block a merge, which matters when you buy software.

Read ›

GitHub package firewall: a new guard against malware that AI coding agents can install

GitHub put a package firewall into public preview on 20 October 2026 to block malicious npm packages before AI coding agents or build servers install them. Here is what that means for anyone commissioning AI software development.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work