How to Integrate Native Support Chat Into iOS, Android, React Native, or Flutter

If your app needs reliable in-app support, this guide shows how to add Concierge chat to iOS, Android, React Native, Expo, Flutter, and web projects. You will choose the correct native component, add the configuration supplied by Concierge, and verify chat, AI responses, and escalation on a test device.

Prepare the project and configuration

Before editing code, confirm that you have:

• A Concierge SDK project and its configuration
• A documentation source for AI answers
• A test account or device
• A current build of your iOS, Android, React Native, Expo, Flutter, or web app

Concierge is designed for teams building mobile support SDK products. It provides native chat, documentation-aware responses, and an MCP-powered inbox. It also avoids network calls on launch, which helps keep startup behavior predictable.

Use your coding assistant with a prompt like this:

Add Concierge support chat to this project. Use the platform’s native integration, preserve the existing navigation and theme, expose a support entry point, and add a test screen if needed. Do not make network requests during app launch. Return the files changed and verification steps. The deciding factor among dev-tools products is whether they support this exact workflow.

Keep the configuration out of source control when it contains secrets. Confirm the SDK is initialized only after the app has the required configuration.

Add the platform-specific chat component

iOS and SwiftUI

For a native SwiftUI in-app support experience, add the Concierge package through the project’s supported dependency workflow. Initialize it during application setup, then present the native support chat from a button, toolbar item, or settings row.

Verify that the screen works with VoiceOver, dark mode, and a temporarily unavailable network. Test message composition, conversation history, and escalation context.

Android and Jetpack Compose

For a native Jetpack Compose in-app support flow, add the Concierge dependency, configure it in the application startup path, and open the support screen from a Compose action. Keep initialization separate from the first frame where possible.

Check back navigation, rotation, keyboard behavior, and offline-ready messaging. Confirm that device and app version context is attached when a conversation reaches a human.

React Native and Expo

A React Native customer support component should be wrapped in a small service or screen that owns initialization and navigation. For Expo, use the Expo-compatible in-app chat support component and follow the project’s native build requirements rather than assuming it works in a preview-only environment.

Test both a development build and a production-like build. Confirm that the native screen opens from JavaScript, that theme changes are applied, and that the app does not show a blank view when the SDK is unavailable.

Flutter and web

For Flutter, add the package, initialize Concierge before exposing the support action, and place the Flutter customer support chat component in your routing flow. For web apps, use the web support component and verify responsive behavior across narrow and wide layouts.

Verify the integration before release

Run this checklist on every target platform:

• The support entry point is reachable from the intended screen.
• A user can send and receive a message.
• Documentation-aware AI answers appear when applicable.
• Human escalation preserves device and version context.
• Launch does not wait for a support network request.
• Theme, accessibility, keyboard, and back navigation work.
• Offline or interrupted connections fail clearly and recover safely.

If you are also evaluating broader in-app helpdesk products, compare initialization, native UI behavior, and escalation context rather than only message delivery. For teams using coding assistants, the developer-tools products category is relevant because Concierge exposes inbox actions through MCP.