Mobile SDKs
Embed the Loops AI assistant natively in your iOS or Android app — chat, virtual try-on, search, size, and analytics through one SDK.
The Loops AI mobile SDKs embed the full assistant inside your native app. Each SDK is a thin, dependency-free container around the Loops web runtime: the web owns the conversation UI, while native owns the session, routing, and analytics.
Both platforms speak the same typed bridge and emit the same canonical
analytics on their own per-platform channel — iOS on ios and Android on
android — so web, iOS, and Android reports share one taxonomy while staying
separable by channel.
Choose your platform
iOS SDK
Swift Package Manager · iOS 15+ · SwiftUI & UIKit.
Android SDK
Gradle · Android 7.0+ (API 24) · Compose & Fragments.
Not on native iOS or Android?
React Native, Flutter, Cordova / Capacitor, Unity, or a dependency policy that rules the SDK out — you can host the same runtime yourself in a WebView. See Mobile WebView (No SDK) for the full URL and message contract, with copy-paste containers per framework.
What you get on both platforms
- Chat presented full-screen, as a sheet/bottom sheet, or pushed onto a stack.
- Flow modes as first-class native calls — virtual try-on, AI search, size suggestion, voice.
- Analytics routed through the SDK on a per-platform channel (
iosorandroid), sharing one taxonomy with your web reports. - Native session ownership — the anonymous session persists natively and survives app relaunch (no session loss on the system WebView).
- Independent on/off per platform — enable or disable iOS and Android separately from the dashboard (Channels tab), without touching the web widget.
The two SDKs are API-mirrored: the same configuration model, flow-mode methods, listener/delegate callbacks, and analytics pipeline exist on both. Differences are only the platform idioms (Swift vs Kotlin, SwiftUI vs Compose). Web embed is documented under Widget Embed.