Google Play Instant Apps Publishing Shutdown — when and how should I migrate?
Mobile teams still relying on Instant Apps need a migration decision for what to replace that distribution path with now that new Instant App publishing ended in December 2025 and related APIs stopped working.
Blockers
- eol_date: capability/instant-apps → n/a
- requires_version: capability/android-app-links → runtime/android-6
- host verification is per-host
- one unverified host can break default-handler verification for all hosts in the manifest
- Dynamic App Links rules in assetlinks.json cannot expand beyond the static manifest scope
- Lock-in via protocol/digital-asset-links
- Lock-in via protocol/digital-asset-links
Who this is for
- cost-sensitive
- small-team
- low-ops
Candidates
Replace Instant entry points with a regular Android app plus Android App Links
As of 2026-03-27, the Google Play Instant shutdown has already occurred: Android Developers states that starting December 2025, Instant Apps cannot be published through Google Play, Google Play services Instant APIs no longer work, and users are no longer served Instant Apps by Play using any mechanism. Google explicitly recommends sending users to the regular app or game and using deeplinks to route them to specific journeys or features. Android App Links is the verified deep-link mechanism for Android 6 and later, using Digital Asset Links hosted on your website so verified URLs open directly in the app. Current Android platform caveats are version-sensitive: on Android 12 and higher, host verification is per-host, while on Android 11 and lower, one unverified host can break default-handler verification for all hosts in the manifest; on Android 15 and higher, Dynamic App Links rules in `assetlinks.json` cannot expand beyond the static manifest scope. Pricing as of 2026-03-27: check official docs, because the Android App Links documentation does not publish a separate product price.
When to choose
Use this when you already have a maintained Android app and want the closest replacement for Instant discovery with the least new platform surface area. It is the default migration path when your goal is to preserve native flows and map old Instant entry URLs to installed-app or Play-install destinations.
Tradeoffs
Keeps a native codebase and follows Google's stated migration guidance, but it no longer offers no-install execution. Success depends on correct domain verification, manifest scope, and link routing behavior across Android versions.
Cautions
You must serve valid `assetlinks.json` over HTTPS for each relevant host, and Play App Signing can affect which certificate fingerprint you need. If multiple activities or multiple apps claim the same verified host and path, routing can be ambiguous or installation-order dependent.
Move lightweight trial or content flows to a PWA packaged with Trusted Web Activity
Trusted Web Activity is Google's documented way to launch a full-screen browser tab without browser UI from an Android app shell, and it is restricted to sites you own. As of 2026-03-27, this is a practical replacement when the old Instant experience was mostly a thin acquisition or preview flow that can live on the web instead of in a native instant module. Verification still uses Digital Asset Links, and if verification fails the experience falls back to a Custom Tab instead of the full Trusted Web Activity presentation. Pricing as of 2026-03-27: check official docs, because the Android documentation for Trusted Web Activity does not publish separate pricing.
When to choose
Use this when the Instant experience was primarily marketing, onboarding, catalog, or other web-suited functionality and you want one code path across web and Android. It is the better replacement than native deep links when maintaining a tiny native slice only for pre-install usage is no longer worth the cost.
Tradeoffs
Reduces native-only surface area and can reuse an existing web app, but it is not a drop-in replacement for native Instant APIs or native-only flows. UX depends on web performance and browser support for Trusted Web Activities.
Cautions
Verification depends on the correct signing key, and Google Play publishing can introduce a different signing key than local builds. If verification fails, users see a Custom Tab with browser UI, so release signing and `assetlinks.json` management become deployment-critical.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Google Play Instant Apps Publishing Shutdown — when and how should I migrate?"