React Native SDK

In-app support for your React Native app

One npm package puts support conversations, bug reports and a feedback board inside your React Native or Expo app. Your team answers from one dashboard; replies stream into the open thread live and arrive as push notifications when the app is closed.

@clariodesk/react-native on npm · Live in 10 minutes · No backend to deploy

How it works

Three calls and you're live

No webhooks, no OAuth dance, no support backend to build. Devices register themselves with hardware-backed keys, so there's no user-auth plumbing either.

1. Install the package

npm install @clariodesk/react-native react-native-get-random-values

# then pick the secure-storage peer for your stack:
npx expo install expo-secure-store   # Expo
npm install react-native-keychain    # bare RN

2. Initialize once at app start

import { ClarioDesk } from '@clariodesk/react-native';

// First launch generates a hardware-backed device key and registers it.
await ClarioDesk.init({ apiKey: 'pk_live_…' });

// Optional — after your own auth knows who the user is. Metadata only:
// the device key is the real identity, so this grants no access.
await ClarioDesk.identify({ externalId: user.id, email: user.email });

3. Open the support UI

Prebuilt and themeable, or skip it entirely and build your own on the headless API.

import { ClarioDeskProvider } from '@clariodesk/react-native/ui';
import { openInbox, openBugReport } from '@clariodesk/react-native/ui';

<ClarioDeskProvider theme={{ primary: brand.accent, mode: 'system' }}>
  <App />
</ClarioDeskProvider>;

openInbox();      // the user's conversations
openBugReport();  // bug report form, screenshot attached automatically
Built for React Native

What's specific to React Native

All three ClarioDesk SDKs share one frozen contract, so every feature behaves the same everywhere. These are the parts that are particular to React Native.

Bare RN and Expo, both architectures

Bare React Native on the old bridge and the New Architecture, Expo dev builds and EAS. You can even evaluate the whole flow in Expo Go before committing to a dev build.

Zero mandatory native code

The prebuilt UI at @clariodesk/react-native/ui is pure JS with its own modal — no react-navigation dependency. Push lives in a separate package so Firebase never autolinks into a host that doesn't want it.

Hooks, not wiring

Live ticket lists and threads come through React hooks that subscribe and clean up on their own. Writes are imperative and optimistic.

What you get

One SDK, the whole customer relationship

Support, bug reports and feedback share one customer record — so the person who joined your waitlist, filed a bug and voted for dark mode is one person, not three strangers.

  • Support conversations with live streaming replies
  • Push notifications when the app is closed
  • Bug reports with device, OS, version, network and logs attached
  • Photos, video and file attachments both ways
  • An in-app feedback board with voting
  • A satisfaction rating on every resolve
  • One-click escalation to a pre-filled Linear issue
  • RevenueCat subscription status on every ticket
Read the React Native quickstart
FAQ

React Native questions, answered

Install @clariodesk/react-native plus react-native-get-random-values and a secure-storage peer, call ClarioDesk.init({ apiKey }) with your publishable pk_live_ key at app start, then wrap your app in ClarioDeskProvider and call openInbox() from anywhere. There is no backend to deploy and no user-auth plumbing — devices register themselves with hardware-backed keys.

Yes. Expo dev builds and EAS are fully supported through the config plugin, and you can evaluate the entire flow in Expo Go before you commit to a dev build. Bare React Native works on both the old bridge and the New Architecture.

Only if you want push. Push notifications ship as a separate package, @clariodesk/react-native-push, precisely because Firebase autolinks native code into every host that installs it. The core package and the prebuilt UI ship zero mandatory native dependencies beyond secure storage.

No. The core package is headless — the same methods and live subscriptions with your own components on top. The prebuilt UI is an optional subpath import you can ignore entirely.

Be first in line when
ClarioDesk launches

We onboard the waitlist in small batches. Early users get hands-on integration help — from a human — and a real vote on what ships next, starting with the feedback board.

No spam, ever. We'll only email you about ClarioDesk.