> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clariodesk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ClarioDesk SDKs

> Drop-in in-app support and bug reporting for Flutter, React Native, and native iOS (Swift), with no backend code on your side.

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.

<CardGroup cols={3}>
  <Card title="Flutter SDK" icon="flutter" href="/flutter/quickstart">
    Add `clariodesk` to your `pubspec.yaml` and ship support in minutes.
  </Card>

  <Card title="React Native SDK" icon="react" href="/react-native/quickstart">
    `@clariodesk/react-native` for bare RN and Expo (dev build + Expo Go).
  </Card>

  <Card title="Swift SDK" icon="swift" href="/swift/quickstart">
    Native iOS via SPM: actor engine, `AsyncStream` reads, SwiftUI prebuilt UI,
    APNs push with no Firebase.
  </Card>
</CardGroup>

## Two ways to integrate

<CardGroup cols={2}>
  <Card title="Headless (primary)" icon="code">
    Promise-based methods plus live subscriptions/streams. You render the UI in
    your own design system. This is the primary integration mode.
  </Card>

  <Card title="Prebuilt UI (secondary)" icon="layout-panel-left">
    A themeable drop-in chat you present with one call: inbox, ticket detail,
    new ticket, and bug report screens.
  </Card>
</CardGroup>

## 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 →](/concepts/authentication)
* **Live updates:** agent replies, status changes, presence, and read receipts
  stream over Centrifugo (falling back to SSE). [Realtime →](/concepts/realtime)
* **Attachments:** photos, videos, and files on any message, both directions.
  [Attachments →](/concepts/attachments)
* **Push notifications:** deep-link straight to the right ticket on tap.
  [Push →](/concepts/push-notifications)
* **CSAT:** an inline satisfaction rating when an agent resolves a ticket.
  [CSAT →](/concepts/csat)

## Next steps

<CardGroup cols={2}>
  <Card title="5-minute quickstart" icon="rocket" href="/quickstart">
    The shortest path from API key to a working ticket.
  </Card>

  <Card title="Core concepts" icon="book-open" href="/concepts/architecture">
    The model behind the SDKs. Read it once and the API explains itself.
  </Card>
</CardGroup>