Skip to main content
ClarioDesk gives your users a live support inbox inside your app. Drop the SDK in, get a hardware-bound device identity and a real ticket thread that streams agent replies in real time, without writing any backend, auth, or realtime code yourself. The Flutter, React Native, and Swift SDKs implement the same contract: identical bytes on the wire, the same feature set and theme surface, expressed in each platform’s idioms. If a capability behaves differently across the three platforms, treat it as a bug.

Flutter SDK

Add clariodesk to your pubspec.yaml and ship support in minutes.

React Native SDK

@clariodesk/react-native for bare RN and Expo (dev build + Expo Go).

Swift SDK

Native iOS via SPM: actor engine, AsyncStream reads, SwiftUI prebuilt UI, APNs push with no Firebase.

​
Two ways to integrate

Headless (primary)

Promise-based methods plus live subscriptions/streams. You render the UI in your own design system. This is the primary integration mode.

Prebuilt UI (secondary)

A themeable drop-in chat you present with one call: inbox, ticket detail, new ticket, and bug report screens.

​
What you get out of the box

  • Device-is-identity auth: a non-extractable hardware keypair (Secure Enclave / Android Keystore) signs every request. No JWTs, refresh tokens, or identity-verification backend to build. How auth works →
  • Live updates: agent replies, status changes, presence, and read receipts stream over Centrifugo (falling back to SSE). Realtime →
  • Attachments: photos, videos, and files on any message, both directions. Attachments →
  • Push notifications: deep-link straight to the right ticket on tap. Push →
  • CSAT: an inline satisfaction rating when an agent resolves a ticket. CSAT →

​
Next steps

5-minute quickstart

The shortest path from API key to a working ticket.

Core concepts

The model behind the SDKs. Read it once and the API explains itself.