Google Play's third-party store rule goes live 22 July — and Android apps are opted in by default

From 22 July 2026, Google will share an Android app's US Play Store listing — name, icon, description, screenshots — with any compliant third-party app store unless the developer explicitly opts out in Play Console, under the Catalog Interoperability policy stemming from the Epic v. Google settlement.

Google’s Play Console documentation confirms that Catalog Interoperability — the policy resulting from the Epic v. Google settlement — takes effect on 22 July 2026. From that date, a developer’s US app store listing (name, icon, description, screenshots and other metadata) is shared automatically with any third-party Android app store that meets Google’s compliance requirements. Developers who take no action are opted in by default; the choice sits in Play Console under Settings > Catalog Settings, with options to publish everywhere, manage participation per store, or opt out entirely, and it can be changed at any time even after the deadline passes.

This isn’t a hypothetical future change — it’s ten days out, self-service, and reversible, which makes it one of the more actionable pieces of Android policy news this year rather than something to just be aware of.

So what

If you commission or maintain an Android app, this is a five-minute check worth doing before the 22nd rather than after: log into Play Console, find Catalog Settings, and decide deliberately whether wider distribution across third-party stores helps or hurts your app’s positioning — rather than defaulting into it by inaction. For most apps competing on discoverability, broader listing exposure is likely a net positive; for anything where brand control, regional exclusivity, or a single-storefront distribution strategy matters, it’s worth opting out explicitly. Either way, it’s the kind of platform-policy detail that’s easy to miss unless someone’s actively tracking Android developer requirements alongside your build. If you need a hand auditing your app’s Play Console settings or planning ahead of platform changes like this, see our iOS & Android development work or get in touch.

← All research

More research.

GitHub secret scanning cuts false alarms for AWS, Google and Alibaba cloud keys and adds a SpaceX detector

GitHub's 5 November 2026 secret scanning update tightens detectors for AWS, Google Cloud and Alibaba keys, relevant to teams building software with AI coding tools that can paste credentials into code.

Read ›

GitHub's Copilot code review can now be managed by API, with review effort levels and AI credit costs shown

GitHub's 6 November 2026 update lets organisations manage Copilot code review by API and see the review effort and AI credits each AI code review used, a sign AI-assisted development is becoming auditable.

Read ›

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

GitHub now reports how often developers act on Copilot code review comments

On 5 November 2026 GitHub added code review metrics, including an addressed rate, to the Copilot usage metrics API. For AI software development buyers, it is the first first-party number for how much AI review feedback is acted on.

Read ›

Dependabot can now keep AI agent skills and prompts up to date

GitHub's Dependabot gained Agent Package Manager (APM) support on 3 November 2026, treating AI agent skills, prompts and instructions as dependencies that need updating like any other 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