# Whereby for Android

Mobile browser is the easiest way in, but Whereby also supports native Android integrations.

### Choose your approach

{% columns %}
{% column %}
**🚀 Android SDK**

Recommended for a more native Android experience and faster setup.

**→** [Start with the Android SDK](https://docs.whereby.com/whereby-for-mobile-development/whereby-for-android/using-wherebys-native-sdk)
{% endcolumn %}

{% column %}
**🔧 WebView**

Best if your app already uses WebView or you want more configuration control.

**→** [Use the WebView approach](https://docs.whereby.com/whereby-for-mobile-development/whereby-for-android/in-android-apps)
{% endcolumn %}
{% endcolumns %}

***

### Compare the options

* The **Android SDK** handles more setup for you and is the quickest way to launch.
* The **WebView** approach gives you greater flexibility, but requires more manual configuration.
* Choose the path that best fits your app architecture and customization needs.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.whereby.com/whereby-for-mobile-development/whereby-for-android.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.