> This page is for version 2025-12-08.
> For other versions, use one of these documentation indexes:
> - 2026-09-29 (default): https://docs.withpersona.com/2026-09-29/llms.txt
> - 2025-12-08: https://docs.withpersona.com/2025-12-08/llms.txt
> - 2025-10-27: https://docs.withpersona.com/2025-10-27/llms.txt
> - 2023-01-05: https://docs.withpersona.com/2023-01-05/llms.txt
> - 2022-09-01: https://docs.withpersona.com/2022-09-01/llms.txt
> - 2021-07-05: https://docs.withpersona.com/2021-07-05/llms.txt
> - 2021-05-14: https://docs.withpersona.com/2021-05-14/llms.txt
> - 2020-05-18: https://docs.withpersona.com/2020-05-18/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.withpersona.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.withpersona.com/_mcp/server.

# Native Mobile Integration vs. WebView

When possible, we recommend using our native [Mobile Integration (v2)](/mobile-sdks) instead of the [WebView Flow](/webview-flow). We do not recommend using WebView unless you have a hard constraint preventing you from using the mobile SDKs.

## Reasons to use native mobile integration

* WebViews are resource-intensive and can lead to degraded performance, especially on older devices. This can manifest as reduced frame rate, longer waiting times, application freezes, and potential memory-related crashes. General performance is superior on the mobile SDKs.
  * Some devices (e.g. iOS) will terminate your WebView if memory consumption is too high. Persona's autocapture flow is memory-intensive, and if overall device resource usage is high, iOS may kill the WebView running the Persona flow, leading to an interrupted user experience.

* WebView requires more engineering effort to integrate. When integrating with WebView, you must manually handle the following:

  * Request API, to make API requests to Persona
  * Response parser, to parse responses from the Persona API
  * Requesting camera permissions ([example](/quickstart-android-webview#handling-permissions))
  * Filepicker API integration, to allow end users to select and upload files from their device

* Autocapture performance is superior on the mobile SDKs. The mobile SDKs use ML libraries provided by Apple and Google, while WebView uses a WebAssembly library that trades performance for cross-device compatibility.

* Loading speed and network resilience. The mobile SDKs have all runtime dependencies preloaded, while WebView needs to load the Inquiry flow runtime while the end user is waiting.

* Mobile SDKs look more native to the consumer app, while WebViews are more clearly browser-based third-party integrations.

## Reasons to use WebView

* You have app size limitations, and using the native mobile SDKs will bring app size over an acceptable threshold.
* You have strict restrictions on what external dependencies are allowed.
* You need to support iOS 12 or earlier. Our mobile SDKs require a minimum OS version of iOS 13.
* You need to embed the Persona flow into a mobile SDK that will be used by your customers, as opposed to a mobile app.