PHParham HatanianPortfolio ↗
DEEPLINKX / use case

Create a platform-aware promoted-app store link

Keep Android and iOS store destinations and their campaign parameters together for a promoted-app call to action.

DeeplinkX 1.5.8 · Source

A promoted-app card can keep platform-specific store destinations together and ask DeeplinkX to choose the matching store action. The sample promotes Instagram with illustrative campaign parameters.

Reusable Flutter example

import 'package:deeplink_x/deeplink_x.dart';

Future<bool> openPromotedAppStore() {
  return DeeplinkX().redirectToStore(
    storeActions: [
      PlayStore.openAppPage(
        packageName: 'com.instagram.android',
        referrer:
            'utm_source=deeplink_x&utm_medium=example&utm_campaign=summer_launch',
      ),
      IOSAppStore.openAppPage(
        appId: '389801252',
        appName: 'instagram',
        campaignToken: 'deeplink_x_example',
        providerToken: 'example_provider',
        affiliateToken: 'example_affiliate',
        uniqueOrigin: 'use_cases',
      ),
    ],
  );
}

Replace demo tracking tokens with the values appropriate to your own authorized campaign and store accounts. Use tokens issued for your own campaign.

Current example behavior

PromotedAppPage retains the Android and iOS actions in one list and calls redirectToStore from its CTA. The widget does not contain platform-selection branches; the utility filters actions by store.platform == currentPlatform.

The utility tries only matching native store actions, with fallback disabled, in supplied order. It returns false when no matching native store action launches. Platforms with no configured matching action do not receive a generic browser destination through this utility.

For a browser fallback, add an explicit listing URL launch in your application after native selection fails.

Configuration and limits

  • Compare the Google Play implementation and iOS App Store implementation for the exact accepted action parameters.
  • Configure the relevant store package and scheme visibility using the Android manifest and iOS Info.plist.
  • Tracking fields are URL inputs. Their presence does not implement conversion analytics, guarantee attribution, or earn affiliate credit by itself.
  • A successful Boolean describes a native store handoff, not an installation or conversion.

UI behavior

  • Android receives the Play Store action with the entire referrer string preserved.
  • iOS receives the configured campaign, provider, affiliate, and origin tokens.
  • Action ordering and current-platform filtering remain intact.
  • A missing store or unmatched platform returns false without an undocumented browser success.
  • Duplicate taps cannot start concurrent redirects; feedback accurately describes the final handoff result.

Source code

All use cases · App-update store selection · Rating destinations

Continue reading