FingerprintJS Android

Lightweight library for device identification and fingerprinting.

Fully written in Kotlin. 100% Crash-free.

Creates a device identifier from all available platform signals.

The identifier is fully stateless and will remain the same after reinstalling or clearing application data.

Check the FingeprintJS iOS – an iOS library for device fingerprinting.

Table of Contents

1. Quick start
2. Usage
3. Playground App

Quick start

1. Add repository

Add these lines to your build.gradle.

allprojects {	
  repositories {
  ...
  maven { url 'https://jitpack.io' }	
}}

2. Add dependency

Add these lines to build.gradle of a module.

This library depends on kotlin-stdlib.

If your application is written in Java, add kotlin-stdlib dependency first (it's lightweight and has excellent backward and forward compatibility).

dependencies {
  // Add this line only if you use this library with Java
  implementation "org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"

  implementation "com.github.fingerprintjs:fingerprint-android:2.0.0"
}

3. Get deviceIDs and fingerprints

Kotlin

// Initialization
 val fingerprinter = FingerprinterFactory.create(context)

// Usage
fingerprinter.getFingerprint(version = Fingerprinter.Version.V_5) { fingerprint ->
    // Use fingerprint
}

fingerprinter.getDeviceId(version = Fingerprinter.Version.V_5) { result ->
    val deviceId = result.deviceId
    // Use deviceId
}

Java

// Initialization
Fingerprinter fingerprinter = FingerprinterFactory.create(context);

// Usage
fingerprinter.getFingerprint(Fingerprinter.Version.V_5, fingerprint-> {
    // use fingerprint
    return null;
});

fingerprinter.getDeviceId(Fingerprinter.Version.V_5, deviceIdResult-> {
    String deviceId = deviceIdResult.getDeviceId();
    // use deviceId
    return null;
});

getFingerprint and getDeviceId methods execute on a worker thread, as well as the lambda you pass to them, so don't forget to post the work to the main thread when needed.

Also the results are cached, so subsequent calls will be faster.

deviceId vs fingerprint

The library operates with two entities.

1. deviceId - is a random and unique device identifier.

Can be used by developers to identify devices to deliver personalized content, detect suspicious activity, and perform fraud detection. Internally it will use Google Service Framework ID, Media DRM ID or Android ID depending on which one is available. This identifier is stable, i.e. it will remain the same even after reinstalling your app. But it will be different after factory reset of the device.

2. fingerprint is a digital device fingerprint. It works by combining all available device signals and attributes into a single identifier. There is a probability that two identical devices will have the same fingerprint.

Which one should I use?

deviceId is guaranteed to be random and should be your first choice for device identification. This identifier can be spoofed though and shouldn't be used in security-focused or fraud detection scenarios.

fingerprint is much harder to spoof and is a safer choice in security-focused use cases.

See the table about stability of each.

Versioning

fingerprint is versioned incrementally; the version should be set explicitly to avoid unexpected fingerprint changes when updating the library.

See full API reference.

Migration from 1.*.* library versions

The library API has undergone some changes in the major version 2. The older APIs are left as deprecated for now, but are planned to be removed in the future releases. For the vast majority of library usage scenarios the migration process will be fast and almost effortless.

Check out Migration to V2 for migration steps and the motivation behind the changes to the API.

Fingerprint Android Demo App

Try the library features in the Fingerprint Android Demo App.

Android API support

fingerprint-android supports API versions from 21 (Android 5.0) and higher.

License

This library is MIT licensed. Copyright FingerprintJS, Inc. 2020-2022.