> For the complete documentation index, see [llms.txt](https://doc.ozforensics.com/oz-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ozforensics.com/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android.md).

# Android

To start using Oz Android SDK, follow the steps below.

1. Embed Oz Android SDK into your project as described [here](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/adding-sdk-to-a-project.md).
2. Get a trial license for SDK on our [website](https://ozforensics.com/developers/try_mobile_sdk) or a production license by [email](mailto:info@ozforensics.com). We'll need your `application id`. Add the license to your project as described [here](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/getting-a-license-for-android-sdk.md).
3. Connect SDK to API as described [here](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/connecting-sdk-to-api.md). This step is optional, as this connection is required only when you need to process data on a server.
4. Capture videos using methods described [here](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/capturing-videos.md). You'll send them for analysis afterward.
5. Analyze media you've taken at the previous step. The process of checking liveness and face biometry is described [here](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/checking-liveness-and-face-biometry.md).
6. If you want to customize the look-and-feel of Oz Android SDK, please refer to [this section](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/customizing-android-sdk.md).

### Resources

Recommended Android version: 7.0+ (API Level 24).

Recommended versions of components:

| Gradle            | 7.5.1  |
| ----------------- | ------ |
| Kotlin            | 1.7.21 |
| AGP               | 7.3.1  |
| Java Target Level | 1.8    |
| JDK               | 17     |

We do not support emulators.

Available languages: EN, ES, HY, KK, KY, TR, PT-BR.

To obtain the sample apps source code for the Oz Liveness SDK, proceed to the GitLab repository:

{% embed url="<https://gitlab.com/oz-forensics/oz-liveness-android>" %}

Follow the link below to see a list of SDK methods and properties:

{% content-ref url="/pages/VCUMVrFbFl9Y2E7Flmdx" %}
[Android SDK Methods and Properties](/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android/android-sdk-methods-and-properties.md)
{% endcontent-ref %}

Download the demo app latest build [here](https://play.google.com/store/apps/details?id=com.ozforensics.liveness.demo\&hl=en).


---

# 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://doc.ozforensics.com/oz-knowledge/guides/developer-guide/sdk/oz-mobile-sdk/android.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.