BlogApp Links

Universal Links vs App Links vs deep links: the 2026 guide

· 6 min read · By the Strait team

Custom URI schemes, Android App Links, iOS Universal Links, intent URLs and deferred deep links compared. What each one is, which opens your app when, the files and code each needs, and how to check your setup.

"Deep link" gets used for at least five different things, and the differences decide whether a tap opens your app or a web page. This guide separates them: what each kind of link is, when the phone opens your app with it, what you have to set up, and where each one breaks.

The short version:

Kind Looks like Opens the app when Without the app
Custom URI scheme yourapp://product/42 The app is installed and claims the scheme An error, or nothing
Android App Link https://links.example.com/p/42 The domain is verified for your app The web page
iOS Universal Link https://links.example.com/p/42 The domain is associated with your app The web page in Safari
Android intent URL intent://…#Intent;…;end Tapped in Chrome or a browser that supports it A fallback URL you choose
Deferred deep link Any of the https forms, plus a service After install, on first open The store, then the screen

A deep link is any link that opens a specific place inside an app instead of its start screen. Everything below is a deep link. Android's own documentation uses "deep links" for the general idea and "Android App Links" for the verified kind (Android Developers: Create deep links).

Custom URI schemes

The oldest form. Your app registers a scheme, such as yourapp, and the phone sends yourapp://… links to it.

They are easy to set up and still useful as a hand-off from a web page to an installed app. But they have two weaknesses:

  • Anyone can claim the same scheme. Apple's documentation says it plainly: "If multiple apps register the same scheme, the app the system targets is undefined" (Apple: Defining a custom URL scheme for your app). Apple recommends Universal Links instead.
  • They fail badly without the app. There is no web page behind yourapp://, so a person without the app gets an error or nothing.

Use a scheme as a private channel between your own web page and your own app, not as the link you share.

An App Link is an ordinary https:// link on a domain that has proved it belongs to your app. Android checks this by fetching https://<domain>/.well-known/assetlinks.json for each host in an intent filter marked android:autoVerify="true" (Android Developers: Verify App Links).

The manifest side:

AndroidManifest.xml
<intent-filter android:autoVerify="true">
  <action android:name="android.intent.action.VIEW" />
  <category android:name="android.intent.category.DEFAULT" />
  <category android:name="android.intent.category.BROWSABLE" />
  <data android:scheme="https" android:host="links.example.com" />
</intent-filter>

The website side lists your package name and the SHA-256 fingerprint of every certificate that signs the app:

/.well-known/assetlinks.json
[{
  "relation": ["delegate_permission/common.handle_all_urls"],
  "target": {
    "namespace": "android_app",
    "package_name": "com.yourco.app",
    "sha256_cert_fingerprints": ["FA:C6:17:…"]
  }
}]

Verification matters more since Android 12. Google's behaviour-change notes say a generic web intent now resolves to your app "only if your app is approved for the specific domain", and otherwise goes to the default browser (Android 12 behaviour changes). In other words, on Android 12 and later an unverified https link opens the default browser, not your app.

The usual failure is a missing fingerprint. An app installed from Google Play is signed with Google's Play App Signing key, not your upload key, so that fingerprint must be in the file too. Our post on the SHA-256 mistakes that break App Links goes through each one.

Check the state on a phone with adb shell pm get-app-links com.yourco.app, or check the file itself with the assetlinks.json checker.

Universal Links are Apple's version: an https link on a domain associated with your app. The app declares the domain in its Associated Domains entitlement (applinks:links.example.com), and the domain serves an apple-app-site-association file.

Two details from Apple's documentation catch people out:

  • Since iOS 14 and macOS 11, devices don't fetch the file from your server directly. They ask "an Apple-managed content delivery network (CDN) dedicated to associated domains" (Apple: Supporting associated domains). Changes can take time to reach phones.
  • The file must be served over https "with a valid certificate and with no redirects".

A minimal file that sends every path to one app looks like this. It is also the shape Strait serves for your link domain, built from the Team ID and bundle ID you save:

/.well-known/apple-app-site-association
{
  "applinks": {
    "apps": [],
    "details": [{ "appID": "ABCDE12345.com.yourco.app", "paths": ["*"] }]
  },
  "webcredentials": { "apps": ["ABCDE12345.com.yourco.app"] }
}

In the app, a Universal Link arrives as a browsing-web user activity:

Swift
func scene(_ scene: UIScene, continue userActivity: NSUserActivity) {
  guard userActivity.activityType == NSUserActivityTypeBrowsingWeb,
        let url = userActivity.webpageURL else { return }
  route(url) // validate the path and parameters before acting on them
}

Apple's own advice applies to both schemes and Universal Links: validate every parameter and don't let a link perform a destructive action (Apple: Supporting universal links in your app).

The AASA validator fetches your file and explains what is wrong with it.

Android intent URLs

Chrome on Android understands a special form:

Code
intent://shop.example.com/product/42#Intent;scheme=yourapp;package=com.yourco.app;S.browser_fallback_url=https%3A%2F%2Fplay.google.com%2F…;end

If the app is installed, Chrome opens it with the data URI. If not, Chrome goes to S.browser_fallback_url (Chrome for Developers: Android Intents with Chrome). The same page notes that Chrome refuses to launch an app from an intent without a user gesture, so a script on a timer won't work.

Intent URLs are what make a link server useful on Android when a tap lands in a browser. Strait answers such taps with an intent URL that opens your app on the right path, or falls back to Google Play with the link kept for after install.

Which one opens the app, and when

What happens to an https link tapped on AndroidIf the domain is verified, the app opens directly. If not, the browser loads the link and the link server can hand it to the app with an intent URL, or send the person to Google Play or the website. https link tapped Domain verified? yes no App opens Browser link server: intent URLto app, Play or website
Android. iPhone follows the same shape with Universal Links, except the fallback is a page in Safari.

Three situations break the happy path on both platforms:

  1. Typed or pasted links. Phones open apps from tapped links. A link pasted into the address bar loads the web page.
  2. In-app browsers. Instagram, Facebook and others often load links in their own web view, which never hands the link to the system. Our post on why Instagram and WhatsApp links open the browser covers the fixes.
  3. No app installed. Every form above needs the app, except a deferred deep link, which carries the link through the store. See deferred deep linking explained.

Which should you use?

  • Share https links, always. App Links and Universal Links work when the app is installed and fall back to a real web page when it isn't.
  • Keep a custom scheme for hand-offs from your own pages to your own app, and treat its parameters as untrusted.
  • Add a deferred deep link service if new users arrive from links: referrals, campaigns, WhatsApp shares. Otherwise the people you most want to convert see your home screen.

With Strait, your link domain serves both verification files from the details in Dashboard → Settings, and the link server makes the intent and store decisions per tap (App Links & Universal Links docs). Universal Links were tested on a real iPhone (iOS 26) in October 2026. When something doesn't open, the troubleshooting guide lists the checks in order.

Sources and how we checked