Clomni

What the Mobile SDK is and who needs it

Last updated: 9 October 2026 · 7 min read

The Clomni Mobile SDK opens Clomni Messenger inside your iOS or Android app. Your users write to your support team without leaving the app. Conversations reach your agents in Clomni next to WhatsApp, Instagram and the website chat. In Clomni, each app is one “Mobile app (App SDK)” channel.

Steps

  1. 1

    What the SDK does

    • Opens the Messenger with native screens, no WebView.
    • Runs the flows you build in Clomni with native buttons: language choice, menus, forms, handover to an agent.
    • Shows an agent's reply as a push notification while the app is closed.
    • Takes colours, logo, texts and news from the dashboard. A change in the dashboard reaches the app without a new release.
    • Also has photo sending in the conversation, an unread count and a CSAT survey after the conversation.

    The SDK adds nothing to your screens by itself. You open the Messenger from your own button, for example a “Support” row on the profile screen. There is a floating button too, but it stays hidden unless you turn it on.

  2. 2

    Who needs it

    Companies with their own mobile app that want to give support inside it: shops, banks, delivery, taxi, games. An administrator creates the channel in the dashboard, and your app's developer adds the SDK to the app.

  3. 3

    Packages and minimum versions

    • Android: ai.clomni:messenger:1.0.5 (Maven Central). Android 6.0 (API 23), Kotlin 1.8, compileSdk 35.
    • iOS: Swift Package https://github.com/clomni/clomni-mobile-sdk.git, version 1.0.4, product ClomniMessenger. iOS 15, Xcode 15.
    • React Native: @clomni/react-native. React Native 0.75 (0.76 for the New Architecture), Expo SDK 52 with a development build.
    • Flutter: clomni_flutter. Flutter 3.16, iOS 15, Android API 24.
    • Unity: https://github.com/clomni/clomni-mobile-sdk.git?path=unity#unity-1.0.5. Unity 2021.3, iOS 15, Android API 23.

    React Native, Flutter and Unity run the native Android and iOS SDKs underneath, so everything works the same on every platform.

  4. 4

    How it is connected

    1. A “Mobile app (App SDK)” channel is created in the dashboard. You get an App ID, an API key per platform and an Identity Secret.
    2. Your server computes a user_hash with the Identity Secret for every signed-in user.
    3. The app adds the package, calls initialize at launch, signs the user in with loginUser and opens the Messenger from your own button.
    4. For push, the Firebase and APNs keys are uploaded to the dashboard, and the device token is given to the SDK.
    5. You check it: “Test a hash”, “Test push” and the first message.

    The path from zero to the first message is in “Mobile SDK: the first 15 minutes”.

  5. 5

    Is the channel on for your account

    The “Mobile app (App SDK)” channel is not on for every account. If Settings › Workspace settings › Inboxes › “Add Inbox” shows no “Mobile app (App SDK)” card in the catalog, the channel is not on for your account yet. The Clomni team turns it on: write “turn on the Mobile SDK for my account” to Clomni AI, and it passes the request to the team.

    If the channel is switched off for the account, the SDK logs this App SDK inbox is switched off in Clomni and the Messenger does not open.

  6. 6

    Network

    The SDK talks to https://app.clomni.ai/v1 over HTTPS and over a WebSocket on the same host. If your company network or MDM profile only lets listed hosts through, add app.clomni.ai.

  7. 7

    Full guide

Document

Clomni Mobile SDK: integration guide v1.0.5 · 72 pages Open Download