Apple's 13 October developer agreement update: what app owners should read before accepting

Apple revised its Developer Program License Agreement on 13 October 2026, adding terms for a Live Assistance API, an App Replacement Entitlement, Apple Home widgets, CarPlay and tax reporting. App owners must accept it to keep publishing.

On 13 October 2026 Apple published a revised Apple Developer Program License Agreement. Until the account holder signs in and accepts it, developers typically cannot submit new builds or update app metadata in App Store Connect. That makes it an operational item, not just legal background.

What Apple says changed

Apple has said translations will follow within a month. The notice gives the headline of each change, not a plain-English reading of what the Live Assistance API or App Replacement Entitlement do, so do not rely on commentary that goes further than Apple’s own text.

Why this matters to buyers

Two things catch businesses out. First, the account holder, often a founder or an ex-employee, is the only person who can accept the agreement. If that person has left, publishing stalls. Second, the tax-reporting and customer-data terms matter if you sell business subscriptions: they sit alongside the 22 October volume purchasing change we covered earlier.

So what

This week, confirm who holds your Apple Developer account, that the account email is monitored, and that someone has read Section 3.2 and the tax terms. If you are planning B2B subscriptions, widgets or CarPlay, check the new terms before scoping the work. Our iOS and Android development services cover store compliance as part of every release, and you can start a project if your app needs a compliance review.

← 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 ›

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.

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 ›

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