> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/nfc-wallet-sdk-android/general/mobile-os-compatibility.md).

# Mobile OS compatibility

NFC Wallet SDK for Android supports a defined set of Android versions.

Thales validates each Android update against the latest NFC Wallet SDK release.

## Supported Android versions by SDK release

Each NFC Wallet SDK release defines the supported Android versions, including the minimum version.

For the requirements that apply to latest SDK version see [Supported configurations](https://gitlab.sre.ops.gcloud.thalescloud.io/bps/gitbook/nfc-wallet-gitbook-docs/-/blob/dev-sdk/NFC-Wallet-SDK-Android/get-started/configuration/1.-binary-integration#supported-configurations).

See release notes for other SDK release.

## Android versioning

{% hint style="info" %}
Android version numbering is defined by Google and may change.
{% endhint %}

Google publishes beta versions before the public release. Use them to validate your digital wallet application early:

* The number and cadence of betas depend on Google’s release plan.
* The public release date can change based on beta feedback.

## Android compatibility status

| Version                   | Release date | Status |
| ------------------------- | ------------ | ------ |
| Android 17 QPR1 Beta 5    | 2026-06-23   | OK     |
| Android 17 Public release | 2026-06-16   | OK     |

Last updated: July 2026


---

# 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.payments.thalescloud.io/nfc-wallet-sdk-android/general/mobile-os-compatibility.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.