Skip to main content
Use this guide to prepare a React Native integration while the Threetone mobile session contract is pending. There is no verified Threetone React Native package or supported native session recipe to install from this guide.

​
Prepare the application

1

Keep workspace access on the server

Identify which signed-in user may use which agent. Keep workspace API keys out of the application bundle, device logs, and client configuration. The application will need the released scoped session-access mechanism before it can connect.
2

Design permission states

For an Android voice interface, review the manifest and runtime handling for RECORD_AUDIO. React Native’s PermissionsAndroid distinguishes granted, denied, and never-ask-again results. Provide a useful recovery message for each denied state.On iOS, supply a clear microphone usage description. Request access as part of an intentional voice action. Text-only interfaces should not request microphone access without a voice feature that needs it.
3

Define lifecycle ownership

Choose the screen or service that owns the session. Use AppState to observe foreground and background changes, then follow the released transport’s pause, end, or reconnect rules. Remove subscriptions when their owner unmounts.

​
Device acceptance checks

Run these checks on physical iOS and Android devices once a supported transport is available. Record the framework version, OS versions, native dependencies, and session contract used for the test. A browser demo inside a WebView does not establish native package support or background audio behavior. Continue with mobile deployment and current availability.

​
Frequently asked questions

Wait for an official package and versioned installation guide. No package name or installation command is established here.
No. It reports application state. Background execution and audio require their own platform support and a verified transport lifecycle.