DocumentationUpgrading

DobroDesk SDKs | Web and native mobile supportIntegrate DobroDesk support into your website or app with native iOS and Android UI plus Flutter, React Native, NativeScript and Capacitor wrappers.
Integrate the DobroDesk web widget SDKInstall the browser SDK, open the widget from your own control and keep customer identity in your backend.
Integrate the DobroDesk iOS SDKAdd the binary Swift Package release, create the native client and present the shared widget from a view controller.
Integrate the DobroDesk Android SDKInstall the published Android bundle, register its local Maven repository and present the native widget from an Activity.
Integrate the DobroDesk Flutter SDKAdd in-app customer support with dobrodesk_sdk, a host-issued customer token and the native iOS or Android widget.
Integrate the DobroDesk React Native SDKInstall the React Native wrapper, provide a signed identity provider and present the native widget through the new architecture bridge.
Integrate the DobroDesk NativeScript SDKInstall the NativeScript wrapper, register its bundled Android repository and present the native widget from a foreground frame or activity.
Integrate the DobroDesk Capacitor SDKInstall the Capacitor wrapper, sync the native project and present the native widget from a hybrid app.
Secure user identity in the DobroDesk SDKsUse a host backend endpoint for short-lived customer identity tokens across web and native integrations.
Customize the widget and mobile SDKs consistentlyShare the DobroDesk appearance contract across web and native surfaces and add narrow platform overrides only when needed.
Handle offline delivery and retries in the SDKsPreserve pending messages through network loss, refresh the same identity and retry only after an explicit acknowledgement boundary.
Enable optional push and voice capabilitiesAdd push or voice only when the host wants the extra native permissions, provider setup and lifecycle responsibility.
SDK FAQ and troubleshootingFind platform floors, authentication rules, lifecycle limits and the first checks for common integration failures.
Web widget SDK: API referenceWeb widget: Typed browser APIs for the DobroDesk loader, widget lifecycle, appearance, events and host actions.
iOS SDK: API referenceiOS: Native APIs for customer identity, signed transport, widget lifecycle, retries and offline message delivery in your mobile app.
Android SDK: API referenceAndroid: Native APIs for customer identity, signed transport, widget lifecycle, retries and offline message delivery in your mobile app.
Flutter SDK: API referenceFlutter: A typed bridge to the shared native iOS and Android engines for the selected mobile framework.
React Native SDK: API referenceReact Native: A typed bridge to the shared native iOS and Android engines for the selected mobile framework.
NativeScript SDK: API referenceNativeScript: A typed bridge to the shared native iOS and Android engines for the selected mobile framework.
Capacitor SDK: API referenceCapacitor: A typed bridge to the shared native iOS and Android engines for the selected mobile framework.
SDK capability matrixSee which conversation, identity, delivery and optional native capabilities are available across the web widget and mobile SDKs.
SDK release notes and versionsReview DobroDesk SDK release notes, check compatible web and mobile versions and pin the right packages for your app.
Upgrade the SDK safelyUpgrade one synchronized SDK release at a time and keep customer identity and pending delivery state intact.

Upgrade the SDK safely

Upgrade one synchronized SDK release at a time and keep customer identity and pending delivery state intact.

Read the release notes for the exact web or mobile version and confirm that your platform floor is still supported.
Bump the native iOS and Android artifacts, framework wrapper and shared mobile protocol together. Pin the versions and update the lockfiles in the same change.
Keep the existing accountScope, signed identity flow and account-scoped outbox during the rollout. Do not clear stored session state as part of a routine upgrade; use the documented reset or logout flow only for an intentional account change.
Run local success and negative flow tests before publishing: install, initialize, present, send, retry, identity isolation, logout or reset and foreground or offline recovery.
Verify light, dark and reduced-motion behavior plus native transitions on each supported host. Roll out only after the updated package, native bundle and changelog describe the same release.

Mobile SDK 0.2.0 and web widget 0.3.1 are the current documented versions. Keep native artifacts, framework wrappers and the shared protocol on the same mobile release.