Skip to main content
A mobile integration must handle application lifecycle and permissions as well as conversation configuration. No verified Threetone mobile SDK release or supported native session contract is established here.

​
Define the application behavior

Document foreground/background transitions, permission denial, audio-route changes, interruption by another call, network loss, and explicit session termination. Decide which state the server owns and which state is only an interface preview. Keep long-lived API keys out of the application binary. Review a server-owned session-access design through authentication. Use events to prepare typed inputs and output handling without inventing SDK methods.

​
Validate the released client

Test a controlled account on supported platform versions and physical devices. Confirm microphone prompts, audio output, reconnect behavior, cleanup, and authorized access. A simulator or visual preview is not sufficient evidence of device audio or server execution. Use SDK resources for current package readiness. Add React Native, Swift, or Kotlin installation steps only with a verified first-party package and compatible runtime release.

​
Frequently asked questions

No. Use a supported server-owned access flow rather than exposing a workspace credential in a distributed application.