Deep linking, framework by framework
How links reach an app built with your framework, what it handles by itself, and what it takes to open the right screen after an install.
- 7 frameworks
- Faster: one prompt per framework
Guides
- / 01ExpoExpo Router, app.json link settings, a development build and EAS signing keys.AndroidiPhone
- / 02Next.jsCreate links in a Route Handler, add Open in app buttons, count tap visits and sales in a client component.WebAndroidiPhone
- / 03FlutterFlowCustom-scheme routing with no code today; exported code and the Flutter SDK for short links and installs.AndroidiPhone
- / 04Capacitor and IonicThe Strait Capacitor plugin, and how links reach a Capacitor app under the hood.AndroidiPhone
- / 05Jetpack Compose (Kotlin)One activity, a NavHost, and link events turned into navigation at the right time.Android
- / 06SwiftUIonOpenURL, onContinueUserActivity and a NavigationStack router.iPhone and iPad
- / 07UnityabsoluteURL and deepLinkActivated, Android manifest and iOS post-build setup, invites that survive install.AndroidiPhone
Not listed?
React Native, Flutter and native apps
Bare React Native, Flutter and Android each have a full set of docs pages: install, receive links, create links, events, test and reference. iOS has one page. Start from Platforms and SDKs. Anything else can use the REST API, which is what every SDK calls.
One link for every app you ship.
Free for 25,000 taps a month, no card.