Platforms and SDKs
One SDK per platform, all following the same contract. Pick yours.
On this page 5
App SDKs
| Platform | Package | What it covers | Start here |
|---|---|---|---|
| React Native | @straitlink/react-native |
Links, deferred links (Play Install Referrer on Android), open reporting | Install & set up |
| Expo (Expo Router) | @straitlink/react-native |
The same SDK, set up through app.json. Needs a development build |
Expo |
| Capacitor / Ionic | @straitlink/capacitor |
A plugin over the Android and iOS SDKs, with the React Native API | Capacitor / Ionic |
| Flutter | strait_sdk |
The same, in pure Dart | Install & set up |
| Android (Kotlin) | strait-sdk-android |
Native Android apps | Install & set up |
| iOS (Swift) | StraitSDK |
Native iOS apps | iOS |
| Unity (C#) | strait-sdk-unity |
Games on Android and iOS | Unity |
React Native, Flutter and Android each have the same pages: Install & set up, Receive links, Create links in the app, Events & revenue, Test and Reference.
Every SDK covers the same ground
Whichever SDK you use, its docs answer the same five questions:
| SDK | Set up | Deep links | Deferred deep links | Events | Common errors |
|---|---|---|---|---|---|
| React Native | Install | Receive links | End to end | Events | Errors |
| Expo | Install | Expo Router | End to end | Events | Errors |
| Capacitor / Ionic | Install | Open a link | Emulator test | Events | Errors |
| Flutter | Install | Receive links | End to end | Events | Errors |
| Android | Install | Receive links | Install referrer | Events | Errors |
| iOS (Swift) | Install | Deep links | Deferred | Events | Errors |
| Unity | Install | Deep links | Deferred | Events | Errors |
| Web | Install | Deep links | Not on the web | Events | Errors |
| Node (server) | Install | Links and opens | Deferred | Events | Errors |
Any error the API sends back is listed in the Error reference, and the limits in Rate limits.
Set up an app with one command
strait init (@straitlink/cli) recognises a React Native, Expo, Flutter or Android app, writes the integration file with your publishable key and link host, and prints the remaining steps for your app. It refuses a secret key. The only existing file it edits is a Flutter or Android app's AndroidManifest.xml, to add the internet permission when it's missing.
npx @straitlink/cli init --key st_pub_live_… --host hilltop.strait.linkWeb and server
| Platform | Package | What it covers | Guide |
|---|---|---|---|
| Web | @straitlink/web |
Website visits and events credited to the tap, smart app banner | Web |
| Node | @straitlink/node |
Create and manage links, send events from your backend | Node |
What's tested
The iOS (Swift) SDK is at version 0.11.7, the Unity SDK at 0.9.7, the React Native SDK at 0.11.6, the Flutter SDK at 0.10.9, the Android SDK at 0.10.7, the Node SDK at 0.8.2 and the web SDK at 0.8.7. Each one's core is checked against the same shared test files: the same link events, app-state labels and offline retry. Two limits today:
- iOS: Universal Links are tested on a real iPhone; install matching after an App Store install is opt-in and proven on iPhone simulators so far.
- Unity: the C# library is tested, but the Unity glue in the guide (MonoBehaviour, PlayerPrefs, the iOS plugin) hasn't been run in the Unity editor or on a device yet.
Every SDK version and what changed in it: Changelog. Not using an SDK? Everything they do is in the REST API.