Mobile Chat SDK: In-App Chat for iOS, Android, React Native and Flutter

A mobile chat SDK is a library you add to your iOS or Android app so users can chat inside the app - with a bot, a human agent, or both - instead of being sent to a website or email. Conferbot ships native SDKs for iOS (Swift), Android (Kotlin), React Native and Flutter. They connect your app to the same chatbot flows, AI agent and team inbox you use on your website and messaging channels.

What every Conferbot SDK includes (version 2.0.0)

• Every flow step: all 82 step types of the flow builder run as they do in the web widget, with native cards for steps such as consent, OTP, address, signature, payment, date and time
• The AI agent and help centre: formatted AI answers with their sources, Helpful? feedback, and your knowledge-base articles inside the app
• Live agent handover: the queue and wait time, help articles and small games while the visitor waits, the agent's live replies and the post-chat rating
• Your dashboard's look: the launcher, greeting card, home screen, theme, colours, fonts and sounds come from the bot's settings, so the app matches your web widget without styling code
• Five languages: the SDK's own words in English, Dutch, French, German or Spanish
• Offline and reconnect: messages sent offline wait and go out when the connection returns, and the conversation is kept across app restarts
• Opt-in push notifications for agent and AI replies: your app passes its FCM or APNs token
• A headless mode when you want to build your own chat UI on top of the SDK

The mobile SDK is available on every plan, including Free. Build the conversation once in the visual builder and it runs in your app and on every other channel.

Version 2.0.0 of all four SDKs was released on 16 October 2026, and React Native 2.0.1 followed on 17 October with a fix for a release-build crash and a choice-step bug. It brings the apps level with the Conferbot web widget: the same flows, live chat, customisation, launcher, languages and help, checked against the widget's own code.

• Flows: all 82 flow step types, including loops and sub-flows, conditions, AI routing and extraction, and knowledge-base answers
• AI agent: starter questions, formatted answers with sources, follow-up questions, Helpful? with reasons, and a notice when a reply takes longer than 45 seconds
• Handover lifecycle: "Connecting you with the team", queue position and wait, a max-wait countdown, leave a message, and a live chat picked back up after a restart
• While you wait: help articles a few seconds into the wait, plus small games
• Home screen and Your requests: the widget's home screen and the visitor's own conversations with your team, with live replies
• Launcher: the web widget's launcher icons, motion and greeting card, and mascots
• Look and feel: the dashboard's theme with dark mode, colours, fonts, sounds and small celebrations such as confetti
• After the chat: the end-of-flow rating and your post-chat redirect URL, shown with a short countdown the visitor can cancel
• Languages: English, Dutch, French, German and Spanish
• Classic UI toolkits: on Android the XML ChatActivity, and on iOS 15+ the UIKit ChatViewController, host the same modern chat, so View- and UIKit-based apps get every feature
• Push: built in and opt-in. Your app hands the SDK its FCM or APNs token, and a tapped notification opens its conversation

Each SDK's CHANGELOG on GitHub lists the changes and the few breaking ones, such as the React Native push call now being setPushToken(token, type).

You can show a web chat widget inside an app with a WebView, but a native SDK fits the app better. The trade-offs are practical rather than theoretical:

A WebView is fine for a quick test. For a support or sales channel your users will rely on, use the native SDK for your stack.

The Conferbot Android SDK is written in Kotlin and supports Android 5.0 (API level 21) and above. It works with Jetpack Compose and with classic XML Views: the XML ChatActivity hosts the same Compose chat, so a View-based app gets every feature without any Compose setup.

Install

The SDK is published on JitPack. Add the JitPack repository (maven { url 'https://jitpack.io' }) to settings.gradle, then the dependency to your app module:

implementation 'com.github.Conferbot:conferbot-android:2.0.0'

Call Conferbot.initialize() in your Application class with your bot id. In Compose, wrap a screen in ConferBotWidgetScope for the floating launcher; from an Activity, Conferbot.openChat(this) opens the full-screen chat.

Highlights

• The web widget's launcher, greeting card and home screen in Compose, and the full chat from XML Views
• Headless mode: every piece of state is a Kotlin StateFlow for your own UI
• Optional FCM push: Firebase is only needed if you want push
• ProGuard and R8 rules ship with the SDK. Requires compileSdk 34, Kotlin 1.9 and JDK 17

More platform detail is on the Android chatbot page.

The Conferbot iOS SDK supports iOS 13 and later with Swift Package Manager (iOS 14 with CocoaPods), Swift 5.7+ and Xcode 14+. The SwiftUI chat, launcher, home screen and help centre need iOS 15; on iOS 15+ the UIKit ChatViewController hosts the same chat, so UIKit apps get every feature.

Install

Add https://github.com/conferbot/conferbot-ios with Swift Package Manager from version 2.0.0 (recommended), or use CocoaPods:

pod 'Conferbot', '~> 2.0'

Call ConferBot.shared.initialize(apiKey:botId:) at launch, then add .conferBotWidget() to a SwiftUI view for the floating launcher, or call ConferBot.shared.present(from:) from UIKit.

Highlights

• SwiftUI and UIKit support
• Opt-in APNs push, with no push or Firebase library in the SDK
• Offline message queue, and conversations kept across launches
• Headless mode: ConferBot.shared is an ObservableObject for your own UI
• Your dashboard's colours, fonts and sounds, with code fallbacks

More platform detail is on the iOS chatbot page.

The Conferbot Flutter SDK (conferbot_flutter on pub.dev) gives one Dart API for iOS and Android apps. Add conferbot_flutter: ^2.0.0 to pubspec.yaml, call StorageService.init() before runApp, create a ConferBotProvider and wrap your home screen in ConferBotFAB for the web widget's launcher. It needs Flutter 3.10+, Dart 3, Android API 24+ and iOS 13+.

• Drop-in: the floating launcher, a full-screen chat, a bottom sheet or the home screen
• Headless SDK: open and close the chat, send messages, pass push tokens and listen to events from your own UI
• Mix and match: use the widgets and drive parts of them from your own code
• Handover: start a live agent handover from code when your app knows the user needs a person

See the Flutter chatbot page for setup details.

The Conferbot React Native SDK (@conferbot/react-native) works with React 17+ and React Native 0.70+, in Expo and bare apps. It is plain TypeScript with no native code of its own, so there is no linking step. Install it with npm install @conferbot/react-native (publishing to npm is in progress; until then install it from the GitHub repository), wrap your app in ConferBotProvider and add ConferBotWidget.

• useConferBot() anywhere in your component tree, with openChat() and closeChat()
• sendMessage() with optional attachments
• setPushToken(token, 'fcm' | 'apns') and handlePushNotification() for opt-in push
• Socket events through on() and off(), including the live agent handover
• A headless mode when you want a fully custom chat UI

See the React Native chatbot page for setup details.

All four SDKs support the same three ways to put chat in your app. Pick by how central chat is to your product.

Whichever pattern you choose, the conversation logic stays in Conferbot, so you can change the flow without shipping an app update.

• Publish the bot in the flow builder: draft flows are not served to the SDK.
• Register push tokens so users see agent replies when the app is in the background.
• Identify the user where your app already knows who they are, so agents do not have to ask.
• Keep the bot flow short on mobile: buttons beat typing on a phone keyboard.
• Test offline: send a message in airplane mode and confirm it arrives when you reconnect.
• Check both themes - the SDKs follow your dashboard theme and the phone's light or dark mode.
• Check the language: the SDK's words follow your widget language or the phone's (English, Dutch, French, German or Spanish).
• Plan the handover: make sure someone on your team watches the live chat inbox during the hours you promise.

Use the SDK that matches the stack your app is already built with.

Need the chatbot outside your app too? The same bot runs on your website and on WhatsApp, Messenger and other channels. For server-side automation, see chatbot API integration.