Universal Links vs deep links: what's the actual difference?

People say "deep link" and "Universal Link" as if they’re the same thing. They’re not, and the mix-up costs real clicks.

"Deep link" is the umbrella — any link that opens a screen inside an app. "Universal Link" is one particular, better-behaved species of deep link that Apple introduced to clean up the older kind. So the honest framing isn’t Universal Links versus deep links; it’s the old style of deep link versus the new one. Here’s what separates them and which you want.

The original deep link is a custom URI scheme: myapp://product/42. Simple — and that simplicity is the bug. Any app can register any scheme. Nothing stops a second app from also claiming myapp://, and when that happens the OS has no principled way to decide who wins. There's also no graceful failure: if the app isn't installed, the scheme resolves to nothing and the user gets an error or a blank stare from their phone.

For years everyone papered over it with timers and JavaScript that tried to guess whether the app had opened. It was flaky and everyone knew it. Apple got tired of it.

Apple’s fix was to stop inventing a new scheme and just use https. A Universal Link is an ordinary web URL — https://yourdomain.com/product/42 — that your app has proven it owns. You host a small file called apple-app-site-association at your domain, list the paths your app handles, and iOS checks it. Now the link is unforgeable: only the app tied to that verified domain can intercept it.

And the fallback comes for free. App installed? iOS opens it. App not installed? It’s still a real https URL, so Safari just loads the page — no detection hacks, no dead end. Android’s equivalent is App Links, the same idea with an assetlinks.json file.

Two reasons. First, plenty of apps and links still lean on the old custom schemes, so the silent-failure behavior is very much alive. Second — the big one — even a proper Universal Link can be undercut by where it's tapped. Inside Instagram's or TikTok's in-app browser, link handling gets strange; the webview can swallow the link or refuse to hand it to the app. Universal Links survive that better than custom schemes, but “better” isn't “always.”

That's the honest state of it: Universal Links and App Links are the right foundation and far more reliable, but the messenger app your link travels through still gets a vote.

If you build the app: Universal Links on iOS, App Links on Android, every time. Keep the custom scheme as a secondary or testing hook, never as the thing a stranger taps.

If you don't own the destination app — you're linking to Instagram, YouTube, Amazon, your Shopify store — you can't set up Universal Links for someone else's app. What you can do is route through a layer that knows each platform's correct open-in-app behavior and falls back cleanly. That's the job directinapp does: one short link that resolves to the right native handoff per platform and drops to web when there's no app, with no association files and no SDK.

Strip the jargon and it’s one sentence: a deep link is the goal, a Universal Link is the reliable way Apple lets you reach it, and a decent fallback is what saves the click when neither fires.