deep-linking

Deep Linking Patterns for Mobile

URI Scheme Design

Design a consistent URI scheme before implementation:

myapp://                          # App root
myapp://home                      # Home screen
myapp://product/{id}              # Product detail
myapp://profile/{userId}          # User profile
myapp://settings/notifications    # Nested settings
myapp://search?q={query}          # Query parameters

Keep paths RESTful, lowercase, and predictable. Use path segments for hierarchy and query params for filters.

Custom schemes are neither unique nor secure — any app can register myapp://. Use them only as an internal/fallback channel; user-facing links should be verified HTTPS App Links (Android) / Universal Links (iOS). Note the parsing asymmetry: in myapp://product/123 the "product" part is the URI host, while in https://www.myapp.com/product/123 it is the first path segment — normalize before routing (see handlers below).

Android

Intent Filter in AndroidManifest.xml

<activity
    android:name=".MainActivity"
    android:exported="true">

    <!-- Custom URI scheme: matches every myapp:// URI.
         Adding android:host would restrict to one host, e.g. myapp://product/... -->
    <intent-filter>
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <data android:scheme="myapp" />
    </intent-filter>

    <!-- App Links (HTTPS, verified via assetlinks.json) -->
    <intent-filter android:autoVerify="true">
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <data
            android:scheme="https"
            android:host="www.myapp.com"
            android:pathPrefix="/product" />
    </intent-filter>
</activity>