Docs

Mobile SDK

Ship the same AI-plus-human support chat you run on the web inside your native Android, iOS, and Flutter apps. One backend contract, one behavior, three platforms.

Platforms#

Three native SDKs share an identical public API surface. Pick the one that matches your app:

SDKStackMinimum
AndroidKotlin, Jetpack ComposeminSdk 24, Kotlin 2.x
iOSSwift, SwiftUI (zero dependencies)iOS 15+, Swift 5.9+
FlutterPure Dart, no native bridgesDart 3.4+, Flutter 3.16+

Each SDK renders a real native chat as a bottom sheet over your app — not a WebView. Your app draws the entry point (a button, an icon, a badge) and opens the chat with Respondo.open().

What's included#

The mobile SDKs mirror the web widget feature set:

  • Chat core: AI agent, live handoff to human operators, typing and read state, file attachments.
  • News feed ("What's new") and onboarding checklists.
  • Surveys (NPS, CSAT, and more).
  • Page-level banners and proactive teasers tied to the current screen.
  • Push notifications for operator replies and campaigns, with deep links into the right conversation.
Product tours and tooltips are web-only surfaces and are not carried over to the mobile SDKs.

How it works#

Every SDK is a thin client for the same public widget contract as the web widget — the backend is reused unchanged. Messaging runs over REST plus a WebSocket, and delivery falls back gracefully (WebSocket, then SSE, then REST polling) and climbs back up the moment the connection recovers.

Authorization is layered:

  • visitor_id — a stable anonymous id the SDK generates and stores in the platform keystore.
  • userHash — an HMAC signature from your backend that binds a conversation to a real person (identity verification).
  • session-token — issued per conversation and replayed on REST and WebSocket calls.

Get started#

Head to the platform page that matches your app — Android SDK, iOS SDK, or Flutter SDK — for install and a working init. Then wire up Identity verification to recognize signed-in users across devices, and Push notifications for offline delivery.

Each SDK installs from its platform registry: Android from Maven Central (ai.respondo:respondo-sdk), iOS via Swift Package Manager from github.com/respondo-app/sdk-ios, and Flutter from pub.dev (respondo_sdk). The Android and iOS sources are public on GitHub.