---
title: Installation
canonical: https://developer.unico.io/dual-api/developers/sdks-and-tools/android/installation/
locale: en
generated_by: markdown-export
---

- [/](/)
- [SDKs and Tools](/dual-api/developers/sdks-and-tools/overview)
- [Android SDK](/dual-api/developers/sdks-and-tools/android/requirements)
- Installation

# Installation

To configure the SDK in your project, follow these steps:

**Step 1** — Add the Maven repositoryThe Android SDK is distributed through Unico's own Maven repository. Add it to the `repositories` block in your **root-level** build file:

- build.gradle.kts
- build.gradle

build.gradle.kts (project)```
allprojects {**  repositories {    google()    maven { url = uri("https://maven-sdk.unico.run/sdk-mobile") }  }}
```

build.gradle (project)```
allprojects {  repositories {    google()    maven { url "https://maven-sdk.unico.run/sdk-mobile" }  }}
```

**Step 2** — Enable AndroidX support (if needed)Add the following to `gradle.properties` at the project root:gradle.properties```
android.useAndroidX=true
```

JetifierFor AGP 8.6+ projects, Jetifier is disabled by default. Only add `android.enableJetifier=true` if your project still depends on legacy `support-library` artifacts that have not migrated to AndroidX — enabling it unnecessarily increases build time.
**Step 3** — Add the SDK dependencyAdd `acessobio-android` to the `dependencies` block in your **module-level** build file. Replace `<latest_version>` with the current version (**6.10.1**) — see [Release Notes](/developers/sdks-and-tools/android/resources/release-notes) for the latest:build.gradle.ktsbuild.gradleapp/build.gradle.kts (module)```
dependencies {  implementation("com.acesso:acessobio-android:<latest_version>")}
```

app/build.gradle (module)```
dependencies {  implementation 'com.acesso:acessobio-android:<latest_version>'}
```

Legacy artifact namingThe Maven group `com.acesso` and artifact name `acessobio-android` reflect legacy Acesso Digital branding — these are the published artifact identifiers and will not change for this SDK version. The same SDK is referred to as **UnicoCheck** in the API Reference and other Unico materials.
**Step 4** — Set Java compatibilityRequired for compatibility with the SDK's minimum supported API level (26). Add the following to `compileOptions` in the same module-level build file:build.gradle.ktsbuild.gradleapp/build.gradle.kts (module)```
android {  compileOptions {    sourceCompatibility = JavaVersion.VERSION_1_8    targetCompatibility = JavaVersion.VERSION_1_8  }}
```

app/build.gradle (module)```
android {  compileOptions {    sourceCompatibility JavaVersion.VERSION_1_8    targetCompatibility JavaVersion.VERSION_1_8  }}
```

**Step 5** — Add AndroidManifest permissionsAdd the minimum required permissions and hardware feature declaration to your `AndroidManifest.xml`:AndroidManifest.xml```
<uses-feature android:name="android.hardware.camera" android:required="true" /><uses-permission android:name="android.permission.INTERNET" /><uses-permission android:name="android.permission.CAMERA" />
```

Play Store delivery filteringThe `<uses-feature>` declaration signals to the Play Store that the app requires a camera, filtering it out for devices that lack one. Set `android:required="false"` only if your app has a camera-free fallback path.Runtime permissionYour app is responsible for requesting the `CAMERA` permission from the user at runtime before opening a capture session. Without a granted permission, the SDK will not be able to open the camera.WebView scenarioSome hybrid apps use the native Android SDK for standard biometric flows while rendering specific journeys (such as custom onboarding flows or region-specific experiences) through the Web SDK inside a WebView. If your app follows this pattern, additional permissions are required. Refer to the [Web SDK integration guide](/developers/sdks-and-tools/web) for the full list.Last updated on Oct 8, 2026**