Mobile deep links in 2026
Universal Links, App Links, Branch, Firebase Dynamic Links — what's alive and what to use in 2026.
A deep link is a URL that opens a specific screen in an installed app, such as a product, an order or a chat, instead of just launching the app on its home screen. If the app isn't installed, the same link should lead somewhere sensible: the website or the store page. Deep links matter for marketing campaigns, sharing, email and push notifications, password resets and magic-link logins. When they break, users land on the wrong screen or in a browser, and nobody notices until a campaign underperforms.
The current toolkit
Universal Links (iOS) and App Links (Android) are the foundation. They're ordinary https URLs on your domain. The operating system checks that your app and your domain belong together, then opens the app directly when it's installed. Verification works through two files on your domain:
/.well-known/apple-app-site-associationlists your app ID and the paths the app handles./.well-known/assetlinks.jsonlists your Android package name and the fingerprints of your signing certificate.
Both must be served over https, without redirects and as JSON. If verification fails, links quietly open in the browser instead.
Attribution platforms such as Branch, AppsFlyer OneLink and Adjust sit on top of these mechanisms. They add deferred deep linking (taking a user to the right screen after they install the app from the link), campaign attribution, link management for marketers and smart fallbacks. They're worth it when marketing runs many campaigns. Pricing and data-processing terms differ by vendor, so check the current plans.
Custom URL schemes like myapp://order/42 still work, but any app can register the same scheme, and there's no web fallback. Use them for internal navigation or callbacks from your own tools, not for links you send to users.
Firebase Dynamic Links is gone
Google deprecated Firebase Dynamic Links and has since shut the service down. Dynamic Links URLs, including those on page.link subdomains, no longer route users into apps. If old emails, QR codes, ads or printed materials still contain them, those links are dead. Migration looks like this:
- Find every place that generated or embedded Dynamic Links: backend code, email templates, QR codes, ad campaigns.
- Set up Universal Links and App Links on your own domain.
- If you relied on deferred deep linking, choose a replacement: an attribution platform or your own implementation.
- Where you control the old URLs, redirect them to the new links.
What breaks in production
- In-app browsers. Links tapped inside social and messaging apps often open in an embedded browser instead of handing off to your app. Plan a web landing page with a clear "Open in app" button.
- Same-domain navigation. On iOS, tapping a Universal Link from a page on the same domain in Safari usually stays in the browser. Testing from your own website can be misleading.
- Android intent filter conflicts. Without verified App Links, Android may show a chooser or another app catches the link. Make sure
android:autoVerify="true"is set and verification actually passes. - Missing fallback. The app isn't installed and the link leads to a 404 on the website. Every deep-linked path needs a working web page or a redirect to the store.
- Silent config changes. A new CDN, a redirect rule or a changed signing key, and verification stops working without any error in the app.
- Routing inside the app. The link opens the app, the screen requires login, and after login the user lands on the home screen. Keep the pending destination through authentication and onboarding.
Checklist
- Both verification files are served from the production domain over https, with no redirects.
- Every deep-linked path has a web fallback.
- Links are tested on real devices from email, messengers, social apps and the browser, with the app installed and without it.
- Login and onboarding preserve the destination.
- No Firebase Dynamic Links remain in templates or generated content.
- Verification is rechecked after every infrastructure change.
Deep links touch the app, the website and the server at once, which is why they tend to fall between teams. We set them up as part of iOS and Android development and keep them working in ongoing mobile app support.
Links opening the wrong screen, or still pointing to Dynamic Links? Reach us on Telegram or MAX.
Got a project on this topic? Tell us the task — we'll come back with an estimate and a schedule.
Message on Telegram → Message on MAX