> 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/smile-identity-ui/installation.md).

# Installation

### Installation

#### Step 1. Add Mavern Central Repo to project level build.gradle

```
buildscript {
    repositories {
        mavenCentral() // add this
    }
}

allprojects {
    repositories {
        mavenCentral() // add this
    }
}
```

#### Step 2: Add the Smile ID Class Path in the project level build.gradle

```

buildscript {
    dependencies {
        classpath group: 'com.smileidentity', name: 'smile-id-android', version: '1.0.1'
    }
}
```

#### Step 3: Apply the Smile ID Plugin in the module level build.gradle (usually app)

Please add this at the top of your build.gradle file but under the com.android.application level

```
apply plugin: 'com.smileidentity.smile-id-android'
```

#### Step 4: Add the Smile ID SDK as a dependency

The latest version can be found [here](https://central.sonatype.com/namespace/com.smileidentity)

```
implementation 'com.smileidentity:smile-id-ui:<latest_version>'
implementation 'com.smileidentity:smile-id-sdk:<latest_version>'
implementation 'com.smileidentity:netjava:<latest_version>'//
```

*NB: If you have already integrated with the Android SDK only Remove the reference to the Smile ID dependency as the Smile UI will automatically pull the correct version in. and also remember to check the latest version* [*here*](https://search.maven.org/artifact/com.smileidentity/smile-id-ui)

#### Step 5: Required Permissions

Before calling the Smile UI screens make sure the below permissions are allowed by the user

```
<uses-permission android:name="android.permission.CAMERA" />
```

#### **Step 6: Add Smile UI Activities to your application manifest**

```
 <!--id capture-->
 <activity android:name="com.smileid.smileidui.SIDIDCaptureActivity" />
 <!--selfie capture-->
 <activity android:name="com.smileid.smileidui.SIDSelfieCaptureActivity" />
 <!--selfie review screen-->
 <activity android:name="com.smileid.smileidui.SIDReviewActivity" />
```

#### **Step 7: Enable Crash Reporting \_(Recommended)**\_

You may optionally choose to report crashes caused by the Smile ID SDK to Smile ID. Only crashes *caused by Smile ID* will be reported. Enabling Smile ID Crash Reporting will not interfere with any other crash reporting you may be doing for your own app. This feature is opt-in, and disabled by default.

To enable it, simply call the static method from your `Application` or main `Activity` class.

```kotlin
import android.app.Application
import com.smileidentity.libsmileid.utils.CrashReporting.enableSmileIdentityCrashReporting

class YourApplication : Application() {
    override fun onCreate() {
        super.onCreate()
        enableSmileIdentityCrashReporting();
    }
}
```

Disabling crash reporting at runtime is as simple as calling the static method `disableSmileIdentityCrashReporting()`


---

# 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/smile-identity-ui/installation.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.