> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/chat-widget/mobile-sdks.md).

# Mobile SDKs

Embed Pylon's chat widget in your iOS, Android, or React Native application.

## Overview

Pylon's mobile SDKs allow you to embed the chat widget directly in your mobile app, providing users with in-app support without leaving your application.

### Supported Platforms

* **iOS** - Native Swift SDK for iPhone and iPad apps
* **Android** - Native Kotlin SDK for Android devices
* **React Native** - Cross-platform SDK for React Native applications

### Setup

To integrate a mobile SDK:

1. Get your App ID from the [Chat Widget](https://app.usepylon.com/settings/chat-widget) settings ([EU](https://app.eu.usepylon.com/settings/chat-widget))
2. Follow the installation instructions for your platform in the GitHub repository
3. Initialize the SDK with your App ID
4. Set user information when a user logs in
5. Add the chat view to your app's UI

For detailed installation instructions and API documentation, visit the GitHub repository for your platform:

* [iOS SDK Documentation](https://github.com/pylon-labs/sdk-mobile/blob/main/ios/README.md)
* [Android SDK Documentation](https://github.com/pylon-labs/sdk-mobile/blob/main/android/README.md)
* [React Native SDK Documentation](https://github.com/pylon-labs/sdk-mobile/blob/main/react-native/README.md)

### EU Data Hosting

If your organization uses EU data hosting, point the SDK at the EU widget by setting both of these in the SDK config:

* `widgetBaseUrl`: `https://widget.eu.usepylon.com`
* `widgetScriptUrl`: `https://widget.eu.usepylon.com/widget/APP_ID`

## What the SDKs Support

The SDKs load the same chat widget as the web, so your widget's [styling](/pylon-docs/chat-widget/styling.md) and [functionality](/pylon-docs/chat-widget/functionality.md) settings apply. Method names vary slightly by platform; see your platform's README for exact signatures.

**User details:** email and name (both required), avatar URL, account ID or account external ID, and an [HMAC email hash](/pylon-docs/chat-widget/identity-verification.md#hmac-email-hash) for identity verification. You can update or clear the user after login.

**Methods:**

* Open and close the chat window
* Show and hide the chat bubble
* Open a new message, optionally prefilled with text or HTML
* Set custom fields on new issues
* Prefill ticket form fields
* Open a ticket form or knowledge base article

**Events:**

* Widget loaded, initialized, and ready
* Chat opened and closed
* Unread message count changed
* Message received
* Error

### Not Supported in the SDKs

These web widget features aren't available in the mobile SDKs:

* JWT identity verification. Use the HMAC email hash instead.
* `contact_id` / `contact_external_id`
* Setting the widget language (`locale` or `setLocale`)
* `setTheme` (dark mode)
* Push notifications
* `showIssue`, `getCurrentIssue`, and `onActiveIssueChange`
* `setVisibleTicketForms`
* Survey and popup visibility events
* Per-message `customFields` on `showNewMessage`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/chat-widget/mobile-sdks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.