What is the minimum iOS and Android version?

iOS 12 and Android API 21 (Lollipop). This covers over 99% of active devices.

Is SwiftUI and Jetpack Compose supported?

Yes. Both SDKs include native SwiftUI and Jetpack Compose helpers for handling deferred deep link callbacks declaratively.

Do SDKs work offline?

Yes. Deep link handling works offline once cached; analytics events are queued and flushed when connectivity returns.

Native deep linking SDKs for every mobile stack

Q: Which platforms are supported?

iOS (Swift), Android (Kotlin/Java), Flutter, React Native, Unity, and Capacitor. All SDKs share the same initialization and callback shape.

Q: What is the SDK package size?

The iOS SDK adds roughly 180KB after App Store compression. The Android SDK adds roughly 150KB. Flutter, React Native, Unity, and Capacitor packages are similarly lightweight.

Ship deep linking on iOS, Android, Flutter, React Native, Unity, and Capacitor — all with the same API shape, the same dashboard, and the same account.

One deep linking API, every stack you ship on

Mobile teams rarely ship on a single platform anymore. A typical product has an iOS app, an Android app, a web fallback, maybe a hybrid Capacitor wrapper for the internal admin, and a Unity build for a marketing mini-game. Historically that meant stitching together three or four deep linking vendors and praying the attribution reconciled. ChottuLink collapses that entire stack into one SDK family with a shared API shape, a single dashboard, and a single billing account.

Every SDK ships as native code — no JavaScript bridge tax, no performance penalty, no runtime surprises. The callback shape is consistent across platforms so your routing logic can be factored into shared code. And because the backend is the same for every SDK, install attribution reconciles automatically across iOS, Android, Flutter, RN, Unity, and Capacitor installs of the same product.

Same callback shape on every platform

// Swift (iOS)
let config = CLConfiguration(apiKey: "your-api-key")
ChottuLink.initialize(config: config)

// Handle resolved deep link
func chottuLink(didResolveDeepLink link: URL, metadata: [String : Any]?) {
    router.navigate(to: link.absoluteString)
}

// Android (Kotlin / Java)
ChottuLink.init(this, "YOUR_API_KEY");

ChottuLink.getAppLinkData(getIntent()).addOnSuccessListener(result -> {
    if (result != null && result.getLink() != null) {
        String link = result.getLink().toString();
        // navigate to link
    }
});

// Dart (Flutter)
await ChottuLink.init(apiKey: "your_api_key_here");

ChottuLink.onLinkReceivedWithMeta.listen((resolvedLink) {
    router.push(resolvedLink.link);
});

// TypeScript (React Native)
ChottuLink.initializeChottuLink('your-api-key-here');

eventEmitter.addListener('ChottuLinkDeepLinkResolved', data => {
    navigation.navigate(data.url, data.metadata);
});

// Init
ChottuLink.Init("your_api_key");

// Handle resolved links via callback
ChottuLink.OnDeepLink += (link) => {
    // Navigate using link.Url
    UnityEngine.Debug.Log("Deep link: " + link.Url);
};

// Init
ChottuLinkIonicSDK.initialize({ apiKey: 'YOUR_API_KEY' })
  .then(() => {
    console.log('✅ ChottuLink initialized successfully');
  })
  .catch((error) => {
    console.error('❌ Error initializing ChottuLink:', error);
  });

// Handle resolved links
ChottuLinkIonicSDK.addListener('onDeepLinkOpen', (data) => {
    console.log('Deep link:', data.url);
    // Navigate to data.url
});

Platform-specific notes

iOS. The SDK registers as a Universal Link handler during init. If your app uses SceneDelegate, pass the incoming userActivity to ChottuLink.continue(userActivity:) in scene(_:continue:). SwiftUI apps can use the .onOpenURL modifier alongside the SDK with no extra wiring.

Android. Add android:autoVerify="true" to the intent filter in your manifest -- this is required for Android App Links to bypass the disambiguation dialog. The Kotlin and Java APIs are identical.

Flutter. The Dart package wraps both native SDKs. The onLink stream fires for both deferred and direct deep links so you handle both in one place. Null safety is supported from Flutter 3.0.

React Native. The package links automatically via the standard RN auto-linking mechanism on RN 0.68 and above. No manual pod install or Gradle edit needed.

Unity. Download ChottuLink.unitypackage and import via Assets → Import Package → Custom Package. During import, enable the mainTemplate.gradle checkbox. If you already have a mainTemplate.gradle, manually add the three required dependencies (gson, okhttp3, installreferrer) to its dependencies block.

Capacitor. On iOS, add the ChottuLinkPlugin to your AppDelegate. On Android, register it in MainActivity. No native code changes beyond the standard Capacitor plugin registration.

Use cases per stack

See how teams on each platform put ChottuLink to work.

Flutter: One Dart handler for iOS & Android

Single onLink stream handles both deferred and direct deep links
No separate Swift or Kotlin handlers needed
Write the routing logic once, run it on every platform

React Native: JS-native deep linking

Generate and resolve share links entirely from JavaScript
Deferred callback fires in the same navigation thread
Smooth handoff from link click to in-app screen

Unity: Session & invite linking in C#

Embed invite or share links anywhere in your game UI
C# callback fires on first launch after install
Route new users directly into the right session or screen

Capacitor: Deep linking without touching native code

TypeScript plugin handles links entirely in web layer
Zero native code changes beyond standard plugin registration
Works for both consumer apps and internal hybrid tools

Frequently Asked Questions

Which platforms are supported? +

What are the minimum supported versions? +

Do the SDKs support SwiftUI and Jetpack Compose? +

What is the SDK package size? +

How does offline deep link handling work? +

Ship deep linking this sprint.

SDK Docs

Native deep linking SDKs for every mobile stack

One deep linking API, every stack you ship on

Same callback shape on every platform

Platform-specific notes

Use cases per stack

Flutter: One Dart handler for iOS & Android

React Native: JS-native deep linking

Unity: Session & invite linking in C#

Capacitor: Deep linking without touching native code

Frequently Asked Questions

Related features

REST APIs

Firebase Migration

Deferred Deep Linking

Seamless Deep Linking

Self-Serve Onboarding

Ship deep linking this sprint.