Current customer SDKs
iOS and FlutterBuild customer context into the product.
Review BTX customer SDKs, desktop and mobile operator apps, developer tools, availability, and the supported capability on each platform.
BTX separates customer-facing SDKs from operator applications. BTXClientKit for iOS and the BTX Flutter SDK are current public integration paths. The Web SDK is in early access, React Native and native Android SDKs are coming soon, and Flutter supports Android applications today. Operators work from the macOS and Windows desktop app, with the native iOS app in controlled rollout.
Current operator app
Desktop for macOS and WindowsAdditional surfaces
Web early access; iOS operator rollout; more coming soonUse customer SDKs inside the product.
The host application enables only the capabilities it needs and identifies a customer only where the experience requires identity. Product teams choose which app and device context is appropriate for support.
Publishable client keys identify the registered customer application. Server credentials do not belong in a customer app bundle.
Customer Messages
Present conversation history or start a new thread from the product surface where help is needed.
Community and feedback
Open native ideas and discussion on iOS, or collect focused product reports with optional media.
Telemetry and flags
Queue structured product events and retain rollout state that changes the customer experience.
Knowledge and notifications
Expose supported knowledge experiences and handle reply notifications through the host platform.
Give operators a purpose-built workspace.
BTX Desktop
Use the complete operator workspace on macOS and Windows for customer, product, knowledge, and integration work.
BTX for iOS
Handle selected customer conversations, context, replies, notifications, and project switching on mobile.
BTX for Android
A native Android operator application is planned and should not be treated as currently shipped.
BTX CLI
Use the command-line package for supported setup and developer workflows where a terminal is the right surface.
Platform availability
| Surface | Platform | Current availability |
|---|---|---|
| BTXClientKit | Native iOS 17+ | Available |
| BTX Flutter SDK | Flutter on iOS and Android | Available |
| BTX Web SDK | Browser | Early access |
| BTX React Native SDK | React Native | Coming soon |
| BTX Android SDK | Native Android | Coming soon; use Flutter for current Android support |
| BTX Desktop | macOS and Windows | Available |
| BTX for iOS | Native iOS operator app | Controlled rollout |
| BTX for Android | Native Android operator app | Coming soon |
Availability is intentionally explicit so an implemented or planned surface is not mistaken for a broadly launched product.
Frequently asked
Does BTX have an Android customer SDK today?
The Flutter SDK supports Android customer applications today. A separate native Android SDK is coming soon.
Are the customer SDK and operator app the same product?
No. Customer SDKs run inside a company’s application. Operator apps are used by the support, success, product, and engineering teams handling customer work.
Where should a developer start?
Start with the public documentation, choose the customer platform, create the matching client configuration, and enable only the capabilities the application needs.