Architecture

All three SDKs are a thin client over the ClarioDesk backend. They own four things (a device identity, a local cache, a realtime connection, and an optional set of prebuilt screens) and expose a small, identical public API on top.

​

The contract is tiny

The SDK keeps all of its state internal and private. Your app’s state management (Riverpod, Bloc, Provider, Redux, Zustand, Context, MobX) is never involved. There are only ever a handful of calls from your app into the SDK:

1. init(apiKey) once at app start.
2. identify({ externalId, email, traits }) when the user logs in or changes.
3. handlePushPayload(...) / openTicketFromPush(...) when a push fires.
4. reset() on logout or user switch.

That’s the entire contract. Your app sends identity and push events in; reads come back to you as live streams (Flutter), subscriptions/hooks (React Native), or AsyncStreams (Swift), not as state you have to wire.

​

Headless vs prebuilt

Both modes ship in the same package. The prebuilt screens are just a consumer of the same headless methods.

​

Routing: the sandbox model

The prebuilt UI never touches your router (GoRouter, Navigator 2.0, React Navigation, Expo Router). Your app pushes one route (a full-screen modal), and the SDK owns a private nested navigator inside it for all internal navigation (inbox → ticket detail → compose → image viewer). Control returns to your app when the user dismisses the modal.

​

Data model

Three objects you’ll touch:

​

Where to go next