> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dashlink.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# App dynamic links

> One link that opens your app when installed and the web when not.

An app dynamic link inspects the device on the way through and decides where to send it: into your native app when installed, to the app store or a custom URL when you configured that for visitors without the app, or to your website (usually `destination_url` on desktop and when no store/custom fallback applies).

One URL works across iOS, Android and desktop, so the same link can go on a poster, in an email, and in a tweet.

## Why not just link to the app store

A store link sends existing users to a page telling them to install something they already have. A dynamic link opens the app they already installed, which is usually the whole point of sending them the link.

## What it needs

**1. A dedicated Dynamic Link domain**

App Link verification is host-wide, so a shared shortlink domain cannot carry an association. Claim a Dashlink subdomain or add your own under Dynamic link domains. See [Branded links](https://docs.dashlink.ai/guides/branded-links/introduction.md).

**2. App association files**

Dashlink copies `assetlinks.json` and the AASA file from your destination website onto the Dynamic Link domain. The app still needs an Android `autoVerify` intent-filter and an iOS `applinks:` entitlement for that host. See [App association](https://docs.dashlink.ai/guides/app-dynamic-links/app-association.md).

**3. Per-platform behaviour on the link**

What to do on iOS, on Android, and when the app is not installed. See [Creating](https://docs.dashlink.ai/guides/app-dynamic-links/create.md).

**4. Optional native SDK (required for deferred)**

Routing works without an SDK. First open after a store install lands on the original content only if a Dashlink SDK is installed: [Android](https://docs.dashlink.ai/guides/app-dynamic-links/android.md), [iOS](https://docs.dashlink.ai/guides/app-dynamic-links/ios.md), or a wrapper that calls those SDKs ([React Native](https://docs.dashlink.ai/guides/app-dynamic-links/react-native.md), [Flutter](https://docs.dashlink.ai/guides/app-dynamic-links/flutter.md), [Unity](https://docs.dashlink.ai/guides/app-dynamic-links/unity.md), [Unreal](https://docs.dashlink.ai/guides/app-dynamic-links/unreal.md)). See [Receive](https://docs.dashlink.ai/guides/app-dynamic-links/receive.md).

> [!WARNING]
>
> Without a verified association on the Dynamic Link domain — and the matching intent-filter / Associated Domains entry in the app — the OS never intercepts the tap. Installed users then follow the browser path (Play Store or custom URL for https App Links).

## They are Shortlinks underneath

App dynamic links are Shortlink records with extra routing, which has three practical consequences:

* An API key granted the `shortlinks` module covers them; there is no separate grant
* They appear in analytics alongside ordinary links
* They can be tagged, added to campaigns, and bulk-managed the same way

## Next

> [card] [Creating](https://docs.dashlink.ai/guides/app-dynamic-links/create.md)
>
> Per-platform behaviour and fallbacks.

> [card] [App association](https://docs.dashlink.ai/guides/app-dynamic-links/app-association.md)
>
> The files iOS and Android need.

> [card] [Receive](https://docs.dashlink.ai/guides/app-dynamic-links/receive.md)
>
> Routing vs deferred, JSON resolve, and which SDK you need.

> [card] [Android SDK](https://docs.dashlink.ai/guides/app-dynamic-links/android.md)
>
> Gradle, App Links, Play Install Referrer, first-open join.

> [card] [iOS SDK](https://docs.dashlink.ai/guides/app-dynamic-links/ios.md)
>
> SPM or CocoaPods, Universal Links, pasteboard first-open.

> [card] [React Native](https://docs.dashlink.ai/guides/app-dynamic-links/react-native.md)
>
> Host allowlist, Linking for live taps, deferred startup call.

> [card] [Flutter](https://docs.dashlink.ai/guides/app-dynamic-links/flutter.md)
>
> Host allowlist, app-links stream, deferred startup call.

> [card] [Unity](https://docs.dashlink.ai/guides/app-dynamic-links/unity.md)
>
> Android and iOS player builds. Editor and desktop return no link.

> [card] [Unreal Engine](https://docs.dashlink.ai/guides/app-dynamic-links/unreal.md)
>
> Android and iOS packages. Editor and desktop return an empty link.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.