Less friction. More destination.
Connect a shared link to a specific place inside your iOS or Android app.
Right past the home screen.
A shared product should open that product. A saved collection should open that collection. Bring people closer to what they came for.
- Universal Links for iOS
- Verified Android App Links
- App paths and store fallbacks
Little details.
A bigger difference.
A deep link points to a specific screen inside an app. LinkRunway resolves the destination and attribution context; your app handles navigation. People without the app follow the fallback you configure.
Configure your app
Register your iOS bundle and team identifiers, or your Android package and signing fingerprints. Verify the branded domain that will serve your app association files.
Open the right screen
Attach an app path to your link. Your app handles the Universal Link or Android App Link, resolves it with the SDK, and navigates to the matching content.
Keep the context
Use Android Install Referrer to carry a signed click token through installation. On iOS, an explicit referral code can reconnect the journey after install with user consent; it does not fingerprint the device.
From a tap to the right place.
Explore an installed-app journey, step by step.
A little introduction.
Someone taps a shared link to content they want to see.
Good questions.
Clear answers.
What happens if the app is not installed?
The link redirects to your platform-specific store or web fallback. Android Install Referrer can recover a signed click after install. On iOS, a consented referral code provides explicit recovery.
Is iOS deferred linking automatic?
No. This implementation uses explicit referral codes for post-install recovery on iOS. It does not fingerprint the device or silently read the clipboard.
Who opens the correct screen?
Your app. Handle the incoming Universal Link or App Link, resolve it with the SDK, validate the returned app path, then navigate using your own router.