Deep links 101: native app vs in-app browser
The plain-English explanation of deep links, universal links, and why Instagram's in-app browser keeps breaking them — without the developer jargon.
A deep link opens a specific screen inside a native app instead of a generic web page. When the app isn't installed, a well-configured deep link falls back cleanly to mobile web. In-app browsers (Instagram, TikTok, Facebook) sit between the tap and the destination and often interfere with this handoff unless the link is built to survive them.
Deep linking is one of those terms creators hear constantly and rarely get a plain explanation of. Here is the version without the developer jargon.
What is a deep link, in plain terms?
A deep link is a URL that opens a specific screen inside a mobile app, rather than just launching the app to its home screen or opening a generic web page. A regular link to a product might open a browser tab. A deep link to the same product opens the Shopify app, Amazon app, or Spotify app directly on that exact product or song page, skipping the browser entirely when the app is installed.
What is the difference between a deep link and a universal link?
A traditional deep link uses a custom URL scheme like myapp://product/123 which only works if the app is already installed and does nothing useful otherwise. A universal link (iOS) or app link (Android) uses a standard https:// URL that intelligently opens the app if installed and falls back to the equivalent web page if not, all from the exact same link. Modern smart link platforms are built around universal and app links specifically because they handle both cases automatically.
What is an in-app browser and why does it complicate deep linking?
An in-app browser is a mini web browser built into apps like Instagram, TikTok, and Facebook, which opens tapped links inside that app's own interface rather than handing the tap off to the phone's default browser or triggering normal app-opening behaviour. Because the tap is intercepted by this sandboxed browser, the operating system sometimes never gets the chance to recognise the link as a deep link and open the target app, even when that app is installed.
Link types compared
| Link type | Opens app if installed | Falls back if not installed | Survives in-app browsers |
|---|---|---|---|
| Plain URL | No | N/A — always web | Yes, but no app benefit |
| Custom scheme deep link | Yes, if app installed | No — breaks silently | Often blocked |
| Universal / App link | Yes | Yes, to web page | Usually, if configured well |
| Smart link with deferred deep linking | Yes | Yes — remembers destination through install | Designed specifically for this |
Why does any of this actually matter for sales?
Native app experiences convert noticeably better than mobile web equivalents for most commerce and content platforms, because the app already has the user’s saved payment details, login, and preferences, removing friction that a mobile browser cannot replicate. Every tap that fails to reach the native app when it could have is a small but real conversion loss, and across thousands of monthly clicks that adds up to meaningful lost revenue.
Do I need to be technical to use deep links in my content?
No. Setting up deep linking through a smart link platform like directinapp is a configuration step in a dashboard, not something you build yourself. The technical complexity of universal links and fallback chains is handled by the platform.
Which apps actually support deep linking?
Most major consumer apps support deep linking, including Amazon, Spotify, YouTube, Shopify storefronts, Instagram itself, and most e-commerce and D2C brand apps. Coverage varies by app, so it is worth checking whether your specific destination app supports it before assuming.
Put this into practice
Create smart short links that open the right app, with analytics built in. No credit card required.
Start free