> For the complete documentation index, see [llms.txt](https://docs.parqex.com/-MUyxAVrX9S4wky8UoX6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parqex.com/-MUyxAVrX9S4wky8UoX6/embedding-parqex-in-native-mobile-apps/overview.md).

# Overview

ParqEx can be easily embedded into a native mobile app using a webview. Some third-party tools integrate into native mobile apps using native mobile SDKs (we previously used this approach), but now our approach to embedding ParqEx in native mobile apps is to use a webview. The main benefits to this approach are:

* Updates and new features for the ParqEx experience are immediately available (whereas updates to native SDKs often lag behind updates for the web experience).
* Updates and new features for the ParqEx experience do not require a new release of your app.
* The user experience is completely consistent between mobile and web.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.parqex.com/-MUyxAVrX9S4wky8UoX6/embedding-parqex-in-native-mobile-apps/overview.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.