When a web page links to an app screen and the app is not installed, the user sees a blank page or an error. Universal Links (iOS) and App Links (Android) solve the installed case but leave the uninstalled case broken unless you plan for it.
The fallback chain
- Try the universal/app link.
- If the app is not installed, the OS falls through to the web URL.
- The web URL should be a full-featured page, not a "download our app" interstitial.
<a href="https://example.com/games/slots">View Slots</a>
The .well-known/assetlinks.json (Android) and apple-app-site-association (iOS) files declare that the app handles this URL pattern. If the app is present, the OS intercepts the navigation. If not, the browser loads the web page normally.
Deferred deep linking
For marketing campaigns, you want the link to work even if the user installs the app after clicking. Store the intended destination in a first-party cookie before redirecting to the app store:
document.cookie = `deferred_route=/games/slots; max-age=3600; path=/; secure; samesite=lax`;
window.location = 'https://apps.apple.com/app/id123456';
On first app launch, check for the cookie (via a shared web view or the clipboard API — with user permission).
An app-forward platform like Lalabet app that lists its catalogue on the web needs seamless handoff — a broken deep link is a lost user, and a "download our app" wall converts at under 2%.
Testing
Test four scenarios: app installed + link clicked, app not installed + link clicked, app installed + link shared via messaging app (which may strip the scheme), and the deferred install flow. Automated testing for the first two is possible with Detox (iOS) and Espresso (Android).
Takeaway
Deep linking is a web-to-native contract. The web page is not a fallback — it is the primary experience for the majority of visitors who do not have the app.
Top comments (0)