Skip to content
Android evaluation

Start with the Android reference app

Explore native document, passport, and face comparison workflows before connecting a capability engine.

These workflows are simulations. The current reference app does not acquire camera or NFC evidence, run inference, store identity evidence, attest a device, or make an identity decision. Android capture and evidence capabilities are still being implemented.

Get the evaluation checkout

Email us your use case, target devices, and the workflow you want to evaluate. The team will arrange repository access and agree on the revision and supported configuration.

Email us for evaluation access

Prepare and build

Use the supplied kenshiki-sdks checkout. The reference app uses JDK 17, Android platform 37.0, and the pinned Gradle wrapper. It runs on Android API 28 or later.

  1. Open reference-apps/android in Android Studio, or build from the repository root with the command below.
  2. Keep the repository structure and pinned dependency verification files intact. Follow reference-apps/README.md for the evaluation revision’s prerequisites.
  3. Run the app from Android Studio on an emulator or device. The simulation needs no backend account, identity document, or camera permission.
bash reference-apps/android/gradlew -p reference-apps/android \
--dependency-verification strict assembleDebug

Build output: reference-apps/android/app/build/outputs/apk/debug/app-debug.apk.

Your first result

Exercise the workflow before the engine

  1. Choose document, passport, or face comparison from the app’s navigation. Start a simulated workflow and follow its steps.
  2. Cancel and restart. In a debug build, use the Developer menu to exercise failure and retry states.
  3. Switch workflows or background the app, then return and explicitly restore the interrupted flow.

First result: your team can examine navigation, interruption, recovery, and simulated completion. The result establishes workflow behavior, not document authenticity, face comparison accuracy, or identity assurance.

Controllers retain state across Android configuration changes. Process-death restoration is not implemented. Real camera, NFC, inference, protected custody, device security checks, and signed-evidence integration require separate implementation and acceptance.

Plan the real integration

Your app owns the experience and permissions; your service owns access decisions. Agree on the capability engine, evidence contract, and failure behavior before treating a simulated outcome as an integration.

For help, email [email protected] with your revision, device and OS, workflow, and error.