RespondKit 0.6.0 — React Native, email follow-up, and attachments

RespondKit 0.6.0 adds a React Native client and brings email follow-up and file attachments to support conversations across web, SwiftUI, Android Compose, and React Native.

• React Native client: native React Native UI, conversation history, read acknowledgements, draft persistence, identity isolation, device context, and native photo/file pickers. The file-picker module requires a native build; use an Expo development build rather than Expo Go.
• Thread email: configure a sender per site/app inbox. Unread operator messages are emailed after a default ten-minute delay, and reading them cancels pending delivery. Replies to the email return to the same customer thread. The minute-based sender normally delivers after 10–11 minutes; emails already handed to the provider cannot be recalled.
• Client improvements: configurable greeting for a fresh session, email collection when no address is known, and native device/OS diagnostics.
• Attachments: multiple files through web file inputs and system photo/document pickers on native clients, stored in private R2. Completed files have no product expiration or configured product size cap; platform limits still apply. Inbound email attachments are not supported.
• Operator and developer tools: optional conversation translation, Discord customer-activity links, refreshed human and agent-readable documentation, and private Paraglide compilers for Apple String Catalogs and Android resources.

AI support-agent credentials/jobs/reply APIs remain a proposal. Localization compilers generate resources, but translated SDK controls and UI language selection are not yet integrated. Host-provided titles/greetings remain host-localized.

Upgrade and compatibility

Use the shared 0.6.0 version for all four npm packages, dev.respondkit:respondkit-core, dev.respondkit:respondkit-compose, and SwiftPM tag v0.6.0 after publication is verified. SwiftUI requires Swift 6 and iOS 18+; Compose requires Android API 26+. React Native peers and installation steps are in its README.

Deploy the compatible API and migrations before rolling out SDK upgrades. Keep old SDKs working during the transition and first upgrade one pilot app. Do not claim email/files work until the target environment has their provider configuration and passes a live smoke test.

Package publication runs through GitHub Actions. The first React Native publication requires one-time npm bootstrap. This release does not deploy the API, configure Cloudflare email/R2, or update host applications.