OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

Android App Links: opening your website's links in your app, and what Android 15 changes

Learn how verified Android App Links connect a website to an app and what to consider before using dynamic rules.

OOmnistu
Reviewed 2026-11-16 · 4 min read
Verified URLs open the app directly
App Links let verified website URLs open matching in-app content without a chooser dialog; users without the app land on your website instead of an error.
Verification ties site to signing key
Android fetches assetlinks.json from your server and checks its sha256_cert_fingerprints against the app's signing certificate.
Android 15 adds server-side rules
Dynamic App Links update deep link rules in assetlinks.json without a new app release; devices with Google services refresh the file periodically.

All wording checked against the Android App Links overview linked in Sources; Android only, nothing tested by us.

If your business has both a website and an Android app, you can make a link to your website open directly in the app for people who have it installed, and open the website for everyone else. Android calls this App Links. This article summarises Google's "About App Links" overview as read on 15 November 2026 (the page says it was last updated 2026-10-28). It is an overview of what the feature is and what to plan, not a setup guide.

What the page says App Links are

How it works, in four steps

  1. The app manifest declares your website URLs in an intent filter with autoVerify set, pointing at your host.
  2. When the app is installed, Android fetches an assetlinks.json file from a known location on your web server.
  3. Android checks the file is valid and that its sha256_cert_fingerprints value matches the app's signing certificate.
  4. When a user taps a matching link, Android sends them straight to the app.

The fingerprint step ties this to your signing setup: if the app signing key changes, the file needs updating. Our article on Android signing keys covers who holds what.

  1. The app manifest declares your website URLs in an intent filter with autoVerify set.
  2. On install, Android fetches an assetlinks.json file from a known location on your web server.
  3. Android checks the file is valid and that its sha256_cert_fingerprints matches the app's signing certificate.
  4. When a user taps a matching link, Android sends them straight to the app.

Dynamic App Links (Android 15 and later)

The page says that from Android 15 you can update deep link rules on the server, in assetlinks.json, without releasing a new app version. Android devices with Google services refresh the file periodically. The file can specify paths, query parameters and fragments, and exclusions that stop certain URLs opening the app. Its example uses are seasonal campaign paths, vanity URLs for partners, A/B testing a URL path, and short-lived events whose rules you delete afterwards.

Points to plan around:

The planning list on the page

Plan which deep links you need and what screen each opens; decide how dynamic rules relate to manifest rules; create and test intent filters; read data from the incoming intent; configure the website association file; test that auto-verification succeeds; and look at the tools in Android Studio and Play Console. The page says the Android App Links Assistant in Android Studio can guide the steps.

App-link verification establishes an app/site association, not user authorization. Sensitive destinations still need normal server-side access checks; a deep link is not a permission to read an order or account.

Omnistu advice for an app project (not from the source)

Limits

One overview page, read in full on 15 November 2026. We did not read the pages on intent filters, verification testing, dynamic rule configuration or backward compatibility, and we tested nothing. We cannot say how many devices have Google services or the reliability fix. Android only; iOS has its own mechanism, which we did not read.

By Omnistu.

Sources

Previous
AI-built prototype databases vs production requirements: avoiding a false BaaS/SQL choice