> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/integration-options/mobile/android.md).

# Android v7 (deprecated)

{% hint style="danger" %}
This SDK is deprecated and will receive limited support. Please adopt the v10 SDK: [https://github.com/smileidentity/docs/blob/main/mobile/android/broken-reference/README.md](https://github.com/smileidentity/docs/blob/main/mobile/android/broken-reference/README.md "mention")
{% endhint %}

### Integration Options

The Android SDK is available in two integration options

### [Smile ID UI Native SDK](https://search.maven.org/artifact/com.smileidentity/smile-id-ui)

This is a quick integration option which has prebuilt screens for Selfie and ID Document capture, This is recommended if you don't have too much customisation requirement for the Selfie and Document capture screens as this is something built to cut down on time to integration and also using our internal recommended integration methods

### [Smile ID Native SDK](https://search.maven.org/artifact/com.smileidentity/smile-id-sdk)

This is the android SDK with all the building blocks on which Smile ID UI builds on and has all the components required to integrate on android. This is recommended if you have specific integration requirements particularly on the UI side where you would need a lot of flexibility compared to what Smile ID UI would allow.


---

# 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, and the optional `goal` query parameter:

```
GET https://legacy-docs.usesmileid.com/integration-options/mobile/android.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.