# deeplinks Published articles for deeplinks. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Scaling with Deeplinks on Android DevFeed: [Scaling with Deeplinks on Android]() Original publisher: [Read original article]() Author: Doximity Published: 2024-04-08T11:34:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [Android](), [Kotlin](), [Code](), [Library]() Tags: [android](), [annotation-processor](), [build](), [code](), [complexity](), [deeplinks](), [dependencies](), [kotlin](), [library](), [manifest](), [mapping](), [module](), [pipeline](), [route]() ### AI overview This tutorial explains how to scale Android deeplink handling as definitions grow from a small set to dozens. It describes reducing router boilerplate with annotations and build-time code generation, and simplifying order-sensitive routing by mapping top-level paths to deeplink definitions. ### Source excerpt Deeplinking support in Android is relatively straightforward. You declare your deeplinks in the app's manifest, receive the incoming Intent passed in to your Activity and then navigate the user to the associated destination. This pipeline works just fine when you only need to support a handful of deeplinks. What happens though as the number of deeplinks grow? How do you deal with several dozen, or possibly even hundreds, of deeplinks? First Stab at Deeplinks When we first implemented deeplinking in our app, we only had to support 12 different deeplinks. We introduced a DeeplinkRouter class that would take the incoming Intent and determine where to navigate the user: interface Deeplink { fun route(uri: Uri): Boolean } class NotificationsDeeplink(val navigator: Navigator) : Deeplink { override fun route(uri: Uri): Boolean { return if (uri.path == "/notifications") { navigator.goToNotifications() true } else { false } } class ProfileDeeplink( val navigator: Navigator, val userRepository: UserRepository ) : Deeplink { override fun route(uri: Uri): Boolean { val profileId = uri.getQueryParameter("id") val isCurrentUser = userRepository.getCurrentUser().id == profileId return if (uri.path == "/profile" && profileId != null) { navigator.goToProfile(profileId, showColleagues = isCurrentUser) true } else { false } } } // ... more deeplink definitions ... class DeeplinkRouter( notificationsDeeplink: NotificationsDeeplink, profileDeeplink: ProfileDeeplink, // ... ) { private val deeplinks = listOf( notificationsDeeplink, profileDeeplink, // ... ) fun route(intent: Intent) { intent.data?.let { uri -> deeplinks.find { it.route(uri) } } } } Problems at Scale As the number of deeplinks and the complexity of their definitions grew, two big issues started to emerge. The first was managing the sheer number of deeplinks - we had nearly 50 at one point! Each of these had to be injected into DeeplinkRouter and then passed to its internal deeplinks list. We decided to resolve this by int ## Using a script to select an Android device for ADB deeplink commands DevFeed: [Using a script to select an Android device for ADB deeplink commands]() Original publisher: [Read original article]() Author: Zarah Dominguez Published: 2023-08-30T00:00:00Z Content type: tutorial Language: en Sources: [Zarah Dominguez]() Topics: [Android](), [Script](), [Emulator]() Tags: [adb](), [android](), [debug](), [deeplinks](), [emulator](), [regex](), [script](), [syntax]() ### AI overview This tutorial explains a script that makes Android Debug Bridge deeplink testing easier when multiple devices or emulators are attached. It lists available devices, prompts for a target when necessary, and sends the command to the selected device. ### Source excerpt Android has a lot of tools for developers and one that has been around for as long as I can remember is Android Debug Bridge (adb). It allows you to issue commands to an attached device, such as installing an app or starting an Activity. ## Debugging App Links in Android 12 🔗 DevFeed: [Debugging App Links in Android 12 🔗]() Original publisher: [Read original article]() Author: Zarah Dominguez Published: 2022-02-08T00:00:00Z Content type: tutorial Language: en Sources: [Zarah Dominguez]() Topics: [Android](), [debug](), [App](), [Website](), [browser](), [API]() Tags: [adb](), [android](), [api](), [browser](), [debugging](), [deeplinks](), [domain](), [figure](), [permission](), [verification]() ### AI overview A tutorial on debugging Android App Links in Android 12. It explains the domain-approval behavior introduced in Android 12 and outlines checks for website association, domain verification, and user permissions using documentation, APIs, and ADB. ### Source excerpt I have been working with deeplinks lately and I noticed that quite a few things have changed since I last worked with them. The most important change is quoted in the list of Android 12 behaviour changes: