Most mobile teams build with cross-platform frameworks. React Native and Flutter dominate, but Kotlin Multiplatform, .NET MAUI, and Capacitor are all growing. These frameworks let you write shared UI and business logic once, then ship to iOS and Android from a single codebase. Deep linking, however, is where the "write once" promise breaks down.<\/p>\n\n\n\n
Deep links require platform-specific configuration on both iOS and Android. You need Apple's This guide covers cross-platform deep linking implementation across React Native, Flutter, Kotlin Multiplatform, .NET MAUI, and Capacitor. You'll find working code, native configuration requirements, navigation patterns, and testing strategies for each.<\/p>\n\n\n\n When a user taps a link on their phone, the operating system decides what happens. If the link matches a registered Universal Link<\/a> (iOS) or App Link<\/a> (Android), the OS opens the app directly. This decision happens at the OS level, before your framework code runs.<\/p>\n\n\n\n That creates a layered problem:<\/p>\n\n\n\n No cross-platform framework handles all four layers for you. Frameworks typically address layer 2 (bridging) and layer 3 (navigation), but layers 1 and 4 remain your responsibility.<\/p>\n\n\n\n For a dedicated deep dive into React Native specifically, see our React Native deep linking setup guide<\/a>. React Native provides the React Navigation accepts a When the app opens via For cases where you need more control (authentication checks, analytics, redirects), you can intercept links before navigation:<\/p>\n\n\n\n Even though your routing logic lives in JavaScript, you still need native setup.<\/p>\n\n\n\n iOS (Xcode):<\/strong><\/p>\n\n\n\n Android ( The Flutter's deep linking story has matured significantly. For a complete Flutter-specific walkthrough, see our Flutter deep linking setup guide<\/a>. The recommended approach uses the When a deep link opens the app, Flutter's engine passes the URL to For authenticated routes or deferred link processing, use iOS<\/strong>: Add Android<\/strong>: Add intent filters in Flutter's documentation on deep linking setup<\/a> walks through each step in detail.<\/p>\n\n\n\n Kotlin Multiplatform shares business logic across iOS and Android while keeping native UIs. Deep link handling typically stays in the platform-specific layer, but you can share the URL parsing logic:<\/p>\n\n\n\n Each platform calls .NET MAUI uses the Capacitor wraps a web app in a native shell. The Capacitor still requires the same native configuration (Associated Domains on iOS, intent filters on Android). The web layer just receives the URL after the native shell intercepts it.<\/p>\n\n\n\n Regardless of your framework, two server-side files are mandatory for verified deep links.<\/p>\n\n\n\n Hosted at Apple's CDN fetches this file when your app is installed (and periodically after). If it's misconfigured, Universal Links won't work at all. The file must be served with Hosted at Android verifies this file during app installation. The SHA-256 fingerprint must match your app's signing certificate. Debug builds use a different certificate than release builds, so you'll need both fingerprints during development. Google's App Links documentation<\/a> covers the verification process.<\/p>\n\n\n\n These files live on your web server, not in your app. Cross-platform frameworks don't generate or manage them. This is one reason teams use a deep linking service: it handles the verification files, fallback logic, and routing configuration in one place, so your server setup stays minimal.<\/p>\n\n\n\n The biggest mistake in cross-platform deep linking is scattering link-handling logic across multiple screens or components. Instead, centralize your routing.<\/p>\n\n\n\n Define a single function or module that maps URLs to navigation actions:<\/p>\n\n\n\n This pattern works identically in Dart, Kotlin, or TypeScript. The router is the single source of truth for URL-to-screen mapping. When you add a new deep link, you add one entry here instead of touching multiple files.<\/p>\n\n\n\n Type safety prevents an entire class of deep link bugs. In TypeScript projects, define your route params as types:<\/p>\n\n\n\n In Dart, use classes or records:<\/p>\n\n\n\n Typed routes make it impossible to navigate to a product screen without an ID, catching mistakes at compile time rather than in production.<\/p>\n\n\n\n Deferred deep linking is the hardest part of cross-platform deep linking. When a user taps a link but doesn't have your app installed, the link context needs to survive the entire install flow: redirect to the app store, download, install, and first launch.<\/p>\n\n\n\n Cross-platform frameworks provide no built-in support for deferred deep links. The app store install process erases URL context entirely. Recovering that context requires a server-side matching service that correlates the pre-install click with the post-install app open using device characteristics (IP address, user agent, device model, timestamp).<\/p>\n\n\n\n Implementing deferred deep linking from scratch involves:<\/p>\n\n\n\n The matching logic needs to handle edge cases: shared Wi-Fi networks (same IP, different devices), VPN users, and time delays between click and install. Probabilistic matching using multiple signals works well in practice, but it requires ongoing maintenance.<\/p>\n\n\n\n This is where a dedicated deep linking service saves real engineering time. Tolinku's deep linking features<\/a> handle deferred deep links out of the box, including the server-side matching, fallback pages, and SDK integration for retrieving the deferred link on first launch.<\/p>\n\n\n\n Testing deep links is notoriously tedious because you can't test them in a simulator's browser the same way they work on a real device. Here's a framework-by-framework testing strategy.<\/p>\n\n\n\n Use React Navigation also provides a Flutter provides the For integration tests, use Automate deep link testing in your CI pipeline:<\/p>\n\n\n\n If you'd rather not maintain verification files, fallback logic, deferred deep linking infrastructure, and per-platform configuration yourself, Tolinku's SDKs<\/a> handle the heavy lifting.<\/p>\n\n\n\n The Tolinku React Native SDK<\/a> wraps the native iOS and Android SDKs and exposes a unified JavaScript API:<\/p>\n\n\n\n The SDK handles the native Universal Links and App Links integration, deferred deep link resolution, and link metadata retrieval. Your routing logic stays in JavaScript.<\/p>\n\n\n\n The Tolinku Flutter SDK<\/a> follows similar patterns using Dart streams:<\/p>\n\n\n\n Both SDKs also work alongside the native iOS SDK<\/a> and Android SDK<\/a>, so if you ever move to fully native development, the same link infrastructure carries over. The Web SDK<\/a> covers the web side, handling smart banners and link routing for your mobile web traffic.<\/p>\n\n\n\n 1. Keep URL patterns consistent across platforms.<\/strong> If 2. Handle missing or invalid parameters gracefully.<\/strong> Deep links come from external sources: emails, push notifications, SMS, social media, QR codes. Users (and bots) will send malformed URLs. Validate parameters and show a helpful fallback screen instead of crashing.<\/p>\n\n\n\n 3. Test on real devices, not just simulators.<\/strong> Universal Links behave differently on physical devices than in the iOS Simulator. The Simulator doesn't fully replicate the AASA verification flow. Budget time for real-device testing before release.<\/p>\n\n\n\n 4. Version your deep link routes.<\/strong> When you rename a screen or change URL structure, keep the old paths working. Broken deep links in emails or saved bookmarks create a terrible user experience. Map old paths to new destinations rather than removing them.<\/p>\n\n\n\n 5. Log deep link events.<\/strong> Track which deep links users tap, whether they resolve successfully, and where failures happen. This data is essential for debugging and for understanding which entry points drive the most engagement.<\/p>\n\n\n\n 6. Don't rely on custom URL schemes for primary deep linking.<\/strong> Custom schemes ( 7. Handle the cold start vs. warm start distinction.<\/strong> When the app is already running and receives a deep link, the behavior differs from a cold start. React Native's Cross-platform deep linking requires work on multiple layers: server-side verification files, native platform configuration, framework bridge code, and in-app navigation routing. No single framework abstracts all of this away, and that's unlikely to change because the native platform requirements are fundamental to how mobile operating systems handle links.<\/p>\n\n\n\n The practical approach is to standardize your URL patterns early, centralize your routing logic, type your route parameters, and test on real devices. For deferred deep links, you'll almost certainly want a service that handles the server-side matching rather than building it yourself.<\/p>\n\n\n\n Whether you're building with React Native, Flutter, Kotlin Multiplatform, or any other cross-platform framework, the deep linking fundamentals are the same. The differences are in the syntax, not the architecture. Get the architecture right, and switching frameworks or adding new platforms becomes a matter of writing new bridge code, not redesigning your link infrastructure.<\/p>\n","protected":false},"excerpt":{"rendered":" Implement deep linking across React Native, Flutter, and other cross-platform frameworks. One guide for all hybrid and native approaches.<\/p>\n","protected":false},"author":2,"featured_media":393,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rank_math_title":"Cross-Platform Deep Linking Guide for 2026","rank_math_description":"Implement deep linking across React Native, Flutter, and other cross-platform frameworks. One guide for all hybrid and native approaches.","rank_math_focus_keyword":"cross-platform deep linking","rank_math_canonical_url":"","rank_math_facebook_title":"","rank_math_facebook_description":"","rank_math_facebook_image":"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/og-cross-platform-deep-linking-guide.png","rank_math_facebook_image_id":"","rank_math_twitter_title":"","rank_math_twitter_description":"","rank_math_twitter_image":"https:\/\/tolinku.com\/blog\/wp-content\/uploads\/2026\/03\/og-cross-platform-deep-linking-guide.png","footnotes":""},"categories":[15],"tags":[25,20,57,24,34,56,30,31],"class_list":["post-394","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-engineering","tag-android","tag-deep-linking","tag-flutter","tag-ios","tag-kotlin","tag-react-native","tag-sdks","tag-swift"],"_links":{"self":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/394","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/comments?post=394"}],"version-history":[{"count":4,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/394\/revisions"}],"predecessor-version":[{"id":2765,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/posts\/394\/revisions\/2765"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/media\/393"}],"wp:attachment":[{"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/media?parent=394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/categories?post=394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tolinku.com\/blog\/wp-json\/wp\/v2\/tags?post=394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}apple-app-site-association<\/code> file, Google's assetlinks.json<\/code>, entitlements in Xcode, intent filters in the Android manifest, and framework-specific bridge code to receive those links in your Dart or JavaScript layer. Every cross-platform framework handles this differently, and none of them abstract it away completely.<\/p>\n\n\n\nThe Cross-Platform Deep Linking Challenge<\/h2>\n\n\n\n
\n
Deep Linking in React Native<\/h2>\n\n\n\n
Linking<\/code> API<\/a> for receiving deep links. Combined with React Navigation's deep linking support<\/a>, you can wire up URL-to-screen mapping with minimal native code.<\/p>\n\n\n\nSetting Up the Linking API<\/h3>\n\n\n\n
linking<\/code> configuration that maps URL paths to screens:<\/p>\n\n\n\n\/\/ App.tsx\nimport { NavigationContainer } from '@react-navigation\/native';\n\nconst linking = {\n prefixes: ['https:\/\/myapp.com', 'myapp:\/\/'],\n config: {\n screens: {\n Home: '',\n Product: 'product\/:id',\n Profile: 'user\/:username',\n Settings: {\n path: 'settings',\n screens: {\n Notifications: 'notifications',\n Privacy: 'privacy',\n },\n },\n },\n },\n};\n\nexport default function App() {\n return (\n <NavigationContainer linking={linking} fallback={<LoadingScreen \/>}>\n <RootNavigator \/>\n <\/NavigationContainer>\n );\n}\n<\/code><\/pre>\n\n\n\nhttps:\/\/myapp.com\/product\/42<\/code>, React Navigation parses the URL, matches it to the Product<\/code> screen, and passes { id: '42' }<\/code> as route params.<\/p>\n\n\n\nHandling Deep Links Manually<\/h3>\n\n\n\n
import { Linking } from 'react-native';\nimport { useEffect } from 'react';\n\nfunction useDeepLinkHandler() {\n useEffect(() => {\n \/\/ Handle link that opened the app (cold start)\n Linking.getInitialURL().then((url) => {\n if (url) handleDeepLink(url);\n });\n\n \/\/ Handle link while app is in foreground (warm start)\n const subscription = Linking.addEventListener('url', ({ url }) => {\n handleDeepLink(url);\n });\n\n return () => subscription.remove();\n }, []);\n}\n\nfunction handleDeepLink(url: string) {\n const parsed = new URL(url);\n const path = parsed.pathname;\n\n \/\/ Check auth, log analytics, then navigate\n if (path.startsWith('\/product\/')) {\n const productId = path.split('\/')[2];\n navigate('Product', { id: productId });\n }\n}\n<\/code><\/pre>\n\n\n\nNative Configuration for React Native<\/h3>\n\n\n\n
\n
applinks:myapp.com<\/code>.<\/li>\nAppDelegate.mm<\/code>, ensure the application:continueUserActivity:restorationHandler:<\/code> method passes Universal Links to React Native. Most React Native templates include this by default.<\/li>\n<\/ul>\n\n\n\nAndroidManifest.xml<\/code>):<\/strong><\/p>\n\n\n\n<activity\n android:name=".MainActivity"\n android:launchMode="singleTask">\n <intent-filter android:autoVerify="true">\n <action android:name="android.intent.action.VIEW" \/>\n <category android:name="android.intent.category.DEFAULT" \/>\n <category android:name="android.intent.category.BROWSABLE" \/>\n <data\n android:scheme="https"\n android:host="myapp.com"\n android:pathPrefix="\/product" \/>\n <\/intent-filter>\n<\/activity>\n<\/code><\/pre>\n\n\n\nandroid:autoVerify="true"<\/code> attribute tells Android to check your assetlinks.json<\/code> file at https:\/\/myapp.com\/.well-known\/assetlinks.json<\/code> to verify ownership.<\/p>\n\n\n\nDeep Linking in Flutter<\/h2>\n\n\n\n
go_router<\/code><\/a> package, which integrates directly with Flutter's Router API<\/a>.<\/p>\n\n\n\nConfiguring go_router<\/h3>\n\n\n\n
\/\/ router.dart\nimport 'package:go_router\/go_router.dart';\n\nfinal router = GoRouter(\n routes: [\n GoRoute(\n path: '\/',\n builder: (context, state) => const HomeScreen(),\n ),\n GoRoute(\n path: '\/product\/:id',\n builder: (context, state) {\n final productId = state.pathParameters['id']!;\n return ProductScreen(id: productId);\n },\n ),\n GoRoute(\n path: '\/user\/:username',\n builder: (context, state) {\n final username = state.pathParameters['username']!;\n return ProfileScreen(username: username);\n },\n ),\n ],\n errorBuilder: (context, state) => const NotFoundScreen(),\n);\n<\/code><\/pre>\n\n\n\n\/\/ main.dart\nimport 'package:flutter\/material.dart';\n\nvoid main() {\n runApp(\n MaterialApp.router(\n routerConfig: router,\n ),\n );\n}\n<\/code><\/pre>\n\n\n\ngo_router<\/code>, which matches the path and renders the correct screen. No manual MethodChannel<\/code> code is needed for basic deep linking.<\/p>\n\n\n\nHandling Deep Links with Guards<\/h3>\n\n\n\n
go_router<\/code>'s redirect feature:<\/p>\n\n\n\nfinal router = GoRouter(\n redirect: (context, state) {\n final isLoggedIn = authService.isLoggedIn;\n final isGoingToLogin = state.matchedLocation == '\/login';\n\n if (!isLoggedIn && !isGoingToLogin) {\n \/\/ Store the deep link destination for after login\n authService.pendingDeepLink = state.uri.toString();\n return '\/login';\n }\n\n if (isLoggedIn && isGoingToLogin) {\n return authService.pendingDeepLink ?? '\/';\n }\n\n return null; \/\/ no redirect\n },\n routes: [ \/* ... *\/ ],\n);\n<\/code><\/pre>\n\n\n\nNative Configuration for Flutter<\/h3>\n\n\n\n
FlutterDeepLinkingEnabled<\/code> as a boolean YES<\/code> in your Info.plist<\/code>, and configure Associated Domains in Runner.entitlements<\/code>:<\/p>\n\n\n\n<!-- ios\/Runner\/Info.plist -->\n<key>FlutterDeepLinkingEnabled<\/key>\n<true\/>\n<\/code><\/pre>\n\n\n\nAndroidManifest.xml<\/code>, just like with React Native. Flutter reads the incoming intent automatically when FlutterDeepLinkingEnabled<\/code> is configured (or when using go_router<\/code>, which handles it internally).<\/p>\n\n\n\nDeep Linking in Other Frameworks<\/h2>\n\n\n\n
Kotlin Multiplatform (KMP)<\/h3>\n\n\n\n
\/\/ shared\/src\/commonMain\/kotlin\/DeepLinkParser.kt\ndata class DeepLinkRoute(\n val screen: String,\n val params: Map<String, String>\n)\n\nfun parseDeepLink(url: String): DeepLinkRoute? {\n val path = url.substringAfter("myapp.com")\n .substringBefore("?")\n .trim('\/')\n\n val segments = path.split("\/")\n return when {\n segments.size == 2 && segments[0] == "product" ->\n DeepLinkRoute("product", mapOf("id" to segments[1]))\n segments.size == 2 && segments[0] == "user" ->\n DeepLinkRoute("profile", mapOf("username" to segments[1]))\n else -> null\n }\n}\n<\/code><\/pre>\n\n\n\nparseDeepLink()<\/code> from its native deep link handler and routes accordingly. On Android, you call it from onCreate()<\/code> or onNewIntent()<\/code>. On iOS, you call it from application(_:continue:restorationHandler:)<\/code>.<\/p>\n\n\n\n.NET MAUI<\/h3>\n\n\n\n
AppAction<\/code> API and custom URI schemes. For App Links and Universal Links, you configure platform-specific handlers in the Platforms\/<\/code> directories and route through the shared App.xaml.cs<\/code>.<\/p>\n\n\n\nCapacitor (Ionic)<\/h3>\n\n\n\n
@capacitor\/app<\/code><\/a> plugin provides appUrlOpen<\/code> events:<\/p>\n\n\n\nimport { App } from '@capacitor\/app';\n\nApp.addListener('appUrlOpen', (event) => {\n const url = new URL(event.url);\n const path = url.pathname;\n\n if (path.startsWith('\/product\/')) {\n router.push(path);\n }\n});\n<\/code><\/pre>\n\n\n\nNative Configuration You Cannot Skip<\/h2>\n\n\n\n
Apple App Site Association (AASA)<\/h3>\n\n\n\n
https:\/\/yourdomain.com\/.well-known\/apple-app-site-association<\/code>:<\/p>\n\n\n\n{\n "applinks": {\n "details": [\n {\n "appIDs": ["TEAMID.com.yourcompany.yourapp"],\n "components": [\n { "\/": "\/product\/*", "comment": "Product pages" },\n { "\/": "\/user\/*", "comment": "User profiles" }\n ]\n }\n ]\n }\n}\n<\/code><\/pre>\n\n\n\nContent-Type: application\/json<\/code> and must not require authentication or redirect. See Apple's Universal Links documentation<\/a> for the full specification.<\/p>\n\n\n\nAndroid Asset Links<\/h3>\n\n\n\n
https:\/\/yourdomain.com\/.well-known\/assetlinks.json<\/code>:<\/p>\n\n\n\n[{\n "relation": ["delegate_permission\/common.handle_all_urls"],\n "target": {\n "namespace": "android_app_namespace",\n "package_name": "com.yourcompany.yourapp",\n "sha256_cert_fingerprints": [\n "AA:BB:CC:..."\n ]\n }\n}]\n<\/code><\/pre>\n\n\n\nNavigation Architecture for Deep Links<\/h2>\n\n\n\n
The Centralized Router Pattern<\/h3>\n\n\n\n
\/\/ deepLinkRouter.ts (React Native)\ntype RouteHandler = (params: Record<string, string>) => void;\n\nconst routes: Array<{ pattern: RegExp; handler: RouteHandler }> = [\n {\n pattern: \/^\\\/product\\\/([a-zA-Z0-9]+)$\/,\n handler: (params) => navigate('Product', { id: params.id }),\n },\n {\n pattern: \/^\\\/user\\\/([a-zA-Z0-9_]+)$\/,\n handler: (params) => navigate('Profile', { username: params.username }),\n },\n {\n pattern: \/^\\\/invite\\\/([a-zA-Z0-9]+)$\/,\n handler: (params) => navigate('AcceptInvite', { code: params.code }),\n },\n];\n\nexport function routeDeepLink(url: string): boolean {\n const path = new URL(url).pathname;\n\n for (const route of routes) {\n const match = path.match(route.pattern);\n if (match) {\n const params = extractNamedParams(match);\n route.handler(params);\n return true;\n }\n }\n return false; \/\/ no match\n}\n<\/code><\/pre>\n\n\n\nTyped Route Parameters<\/h3>\n\n\n\n
type DeepLinkRoutes = {\n Product: { id: string };\n Profile: { username: string };\n Settings: undefined;\n Order: { orderId: string; tab?: 'details' | 'tracking' };\n};\n<\/code><\/pre>\n\n\n\nsealed class DeepLinkRoute {\n const DeepLinkRoute();\n}\n\nclass ProductRoute extends DeepLinkRoute {\n final String id;\n const ProductRoute(this.id);\n}\n\nclass ProfileRoute extends DeepLinkRoute {\n final String username;\n const ProfileRoute(this.username);\n}\n<\/code><\/pre>\n\n\n\nHandling Deferred Deep Links in Cross-Platform Apps<\/h2>\n\n\n\n
\n
Testing Cross-Platform Deep Links<\/h2>\n\n\n\n
React Native<\/h3>\n\n\n\n
npx uri-scheme<\/code> to trigger deep links from the command line:<\/p>\n\n\n\n# iOS Simulator\nxcrun simctl openurl booted "https:\/\/myapp.com\/product\/42"\n\n# Android Emulator\nadb shell am start -a android.intent.action.VIEW \\\n -d "https:\/\/myapp.com\/product\/42" \\\n com.yourcompany.yourapp\n<\/code><\/pre>\n\n\n\nLinkingContext<\/code><\/a> for unit testing link resolution without needing a device.<\/p>\n\n\n\nFlutter<\/h3>\n\n\n\n
--route<\/code> flag for testing initial routes:<\/p>\n\n\n\nflutter run --route "\/product\/42"\n<\/code><\/pre>\n\n\n\nWidgetTester<\/code> to verify navigation:<\/p>\n\n\n\ntestWidgets('deep link navigates to product', (tester) async {\n await tester.pumpWidget(\n MaterialApp.router(routerConfig: router),\n );\n\n router.go('\/product\/42');\n await tester.pumpAndSettle();\n\n expect(find.byType(ProductScreen), findsOneWidget);\n});\n<\/code><\/pre>\n\n\n\nCI\/CD Integration<\/h3>\n\n\n\n
\n
adb shell am start<\/code> commands.<\/li>\nxcrun simctl openurl<\/code>.<\/li>\nassetlinks.json<\/code> with Google's Statement List Tester<\/a>.<\/li>\nUsing Tolinku SDKs for Cross-Platform Deep Linking<\/h2>\n\n\n\n
React Native SDK<\/h3>\n\n\n\n
import { Tolinku } from '@tolinku\/react-native-sdk';\n\n\/\/ Initialize once at app start\nTolinku.init({ apiKey: 'tolk_pub_your_key' });\n\n\/\/ Handle deferred deep links on first launch\nTolinku.getInitialLink().then((link) => {\n if (link) {\n routeDeepLink(link.url);\n }\n});\n\n\/\/ Listen for deep links while app is running\nTolinku.onLink((link) => {\n routeDeepLink(link.url);\n});\n<\/code><\/pre>\n\n\n\nFlutter SDK<\/h3>\n\n\n\n
import 'package:tolinku\/tolinku.dart';\n\nvoid main() async {\n WidgetsFlutterBinding.ensureInitialized();\n await Tolinku.init(apiKey: 'tolk_pub_your_key');\n\n \/\/ Check for deferred deep link\n final initialLink = await Tolinku.getInitialLink();\n if (initialLink != null) {\n \/\/ Route to the intended screen\n }\n\n runApp(const MyApp());\n}\n<\/code><\/pre>\n\n\n\nBest Practices for Cross-Platform Deep Links<\/h2>\n\n\n\n
\/product\/:id<\/code> works on iOS, it should work on Android, and it should work on the web too. Use the same path structure everywhere.<\/p>\n\n\n\nfunction ProductScreen({ route }) {\n const { id } = route.params;\n\n if (!id || !isValidProductId(id)) {\n return <NotFoundScreen message="Product not found" \/>;\n }\n\n return <ProductDetail id={id} \/>;\n}\n<\/code><\/pre>\n\n\n\nmyapp:\/\/<\/code>) have significant limitations: they don't work in many contexts (embedded browsers, some email clients), they can conflict with other apps, and they show error dialogs when the app isn't installed. Use HTTPS Universal Links and App Links as your primary deep linking mechanism.<\/p>\n\n\n\nLinking.getInitialURL()<\/code> only fires on cold start; the url<\/code> event listener only fires on warm start. Flutter's go_router<\/code> handles both, but if you're using manual platform channels, test both scenarios explicitly.<\/p>\n\n\n\nConclusion<\/h2>\n\n\n\n