Build with the Android SDK
Start with a working host app. Capture and recover a document, or watch device evidence change as you move the phone.
Native Android modules inside your app
Add the SDK products your app needs. Your app owns screens, consent and workflow; the SDK returns typed evidence.
- Capture and custody
- Document and selfie capture, protected storage, recovery and erasure.
- Signals and continuity
- Device signal collection and continuity evaluation.
- Evidence signing
- Device signatures, Merkle history and evidence receipts.
Get the evaluation materials
Request SDK repository access, the example apps and their integration guides. Include your use case, target devices and the capability you want to evaluate.
The team will agree the checkout revision, supported configuration and required artifacts with you. Access is arranged by email.
Prepare your checkout
Prepare your Android development environment and a physical device. Use the toolchain and device configuration supplied with your SDK revision.
- Keep the SDK, example projects and native artifacts at the same revision.
- Configure your app identity, signing and protected storage scope for the evaluation.
- Declare the permissions for the capabilities you exercise. Your app owns permission requests, user consent and recovery.
Capture or device evidence
01 · Capture and recover a document
Evaluate document capture, selfie acquisition and protected custody through the SDK.
- Capture the front and back of a test document with camera permission granted.
- Retain both records and note their record IDs.
- Close and relaunch the app, then recover the saved records without reopening the camera.
First result: the saved document records recover with their original IDs. Verify erasure by checking that the records can no longer be recovered.
Continue with selfie, interruption and recovery checks. A saved original establishes retention; document authenticity and identity proofing require separate checks.
02 · Observe device evidence
Evaluate live readings and their availability, then follow an event into the signed history.
- Move the phone and connect a charging cable; inspect motion and power readings.
- Inspect each reading’s source and availability. Denied permission or unsupported hardware should appear as an unavailable input.
- Inspect the event’s payload hash, ledger position, linked roots and device signature.
First result: evidence changes with the physical device, unavailable inputs remain distinct, and a signed receipt binds the event to its history.
For Air check, your app selects the location to corroborate and the acquisition policy.
Use a physical device to accept camera and sensor behavior. Emulator tests and successful builds do not establish that result.
Read the evidence your app receives
Follow an event from its payload hash to the Merkle root and signed receipt.
For evaluation help, email [email protected] with your SDK revision, device and OS, example, and typed error. Keep personal evidence out of the report.