SDK Integration
LimeLink provides direct native iOS and Android SDKs plus React Native and Flutter wrappers for Link resolution, platform link handling, deferred deep links, and explicit event handling.
Current Guides
| Platform | Current guide | Setup model |
|---|---|---|
| iOS | iOS SDK 1.0.1 | Public SwiftPM and CocoaPods integration |
| Android | Android SDK 1.0.1 | Public Maven integration |
| React Native | React Native SDK 1.0.1 | Public npm package; native SDK 1.0.1 dependencies |
| Flutter | Flutter SDK 1.0.0 | Public pub.dev plugin; native SDK 1.0.1 dependencies |
Use Previous Releases only when maintaining an older integration.
Before Integration
- Create or open an Organization and Project.
- Register the corresponding iOS or Android Application in the Project.
- Copy the canonical Project UUID from Project settings for native, React Native, and Flutter SDK initialization.
- Follow the platform or wrapper guide for package installation, app configuration, initialization, and Link callbacks.
- Define an app-owned allowlist of destination schemes and HTTPS hosts before routing any resolved URI.
Plan Boundary
Free includes SDK installation, Universal Links/App Links, and deferred deep links. Pro costs USD $10/month and adds Custom Domains and ad-free links.
Custom Domains require an active Pro Project and additional platform domain association. Add the custom hostname to Android App Links or iOS Associated Domains, publish the platform association file for that hostname, and verify domain association before testing Links. See the current platform guide for exact setup.
Identity and Security Boundary
Initialize native, React Native, and Flutter SDKs with the public Project UUID. It scopes SDK-owned V2 Dynamic Lookup, Deferred, and explicit Stats behavior. Reserve Organization API credentials for trusted server-side integrations.
Open a resolved destination only when its parsed scheme and host exactly match an explicit app-owned allowlist. Version 1.0.1 reports unresolved Universal/App Links as successful results with a nullable deeplinkUrl and the exact inbound HTTPS URL in originalUrl; use that original URL only for an explicitly allowlisted browser fallback.
The public create-Link API remains a separate server-to-server integration. Store its Organization API credential on the trusted server.