# DeeplinkX — typed external app links for Flutter

Canonical HTML: https://p-hatan.com/deeplink-x/

DeeplinkX 1.5.8.

Open a conversation, profile, video, map, meeting, or store listing from your Flutter application using typed Dart actions. DeeplinkX owns the supported providers' link formats and coordinates native, store, and web handoffs where those paths are available.

Use it when your application repeatedly opens supported external apps and you want a consistent API for actions, installation checks, platform-specific configuration, and fallback policy. Choose a general URL launcher when you already have a URL and need a straightforward handoff to a browser or registered scheme handler.

The **X means External**. DeeplinkX launches links out to other apps. Incoming links into your own application need an incoming-link handler and routing setup.

### What it provides

- Typed provider/action constructors instead of assembling supported app URLs throughout your widgets.
- Native app launching and installation checks on applicable platforms.
- Optional store fallback, action-specific web fallback, and a native-only launch option.
- Shared map helpers for view, search, address directions, and coordinate directions where each provider supports them.
- Ordered selection among platform-matched stores for an application listing.
- A federated Flutter plugin targeting Android, iOS, macOS, Windows, Linux, and web, with provider-specific native support and fallback differences.

Browse **42 apps and 7 stores**, including maps, messaging, social apps, and store listings. TomTom GO Expert is experimental.

### Explore and install

- [Package and installation](https://pub.dev/packages/deeplink_x)
- [API reference](https://pub.dev/documentation/deeplink_x/latest/)
- [Source and issue tracker](https://github.com/DeepLinkX/DeeplinkX)
- [Runnable web demo](https://deeplinkx.github.io/DeeplinkX/)
- [Android demo downloads](https://github.com/DeepLinkX/DeeplinkX/releases/latest)

Start with getting started, choose an app/action reference, or follow a practical use-case recipe. Native checks and provider behavior require native execution; a browser demo is not a substitute for device validation.

