Specifications¶
Requirements¶
There are some requirements that your application must meet in order to integrate the XpressID module into it.
- The minimum operating system version is:
Android 10. - The required permissions your application must include are:
Camera,Record AudioandLocation.
Warning
Please, make sure to use a physical device to run the application that integrates this SDK. The SDK cannot be run using simulators.
Module size¶
The following table shows the estimated final compressed contribution of the SDK in an Android app. It is intended to approximate the footprint of the final packaged artifact as stored and distributed through the Google Play Store.
Total final compressed contribution of XpressID to an Android app: 17.83 MB
| Artifact | Version | Final compressed contribution |
|---|---|---|
| platform-common-definitions | 1.0.0 | 0.53 MB |
| platform-common-utils | 1.1.1 | 0.17 MB |
| platform-common-image-manipulation | 1.1.0 | 3.35 MB |
| platform-communication-core | 1.0.1 | 2.28 MB |
| platform-communication-okhttp | 1.0.0 | 0.34 MB |
| genuine-ds | 1.0.1 | 1.91 MB |
| platform-nativeds | 1.1.1 | 2.72 MB |
| sdk-core | 1.1.0 | 4.81 MB |
| sdk-camera | 1.2.0 | 0.58 MB |
| sdk-document | 1.0.2 | 0.20 MB |
| sdk-selfie | 1.0.2 | 0.29 MB |
| sdk-video | 1.0.1 | 0.22 MB |
| sdk-xpressid | 2.0.1 | 0.43 MB |
| Total | 17.83 MB |
Configuration model¶
The current native SDK uses the API v3 payload and separates configuration into four concerns:
flowSetup: onboarding behavior, stages, and capture-specific options.setup: global flags and shared UI behavior.texts: user-facing copy and accessibility labels.medias: logos, illustrations, and reference assets.styles: design tokens and component appearance.
This model should be used for all new integrations. Legacy flat customization keys should be considered deprecated and migrated before a production rollout.
Compatibility¶
XpressID for Android is developed and verified as a native Android SDK distributed as standard .aar libraries. This is the recommended integration path for applications built with Views or Jetpack Compose.
If your product uses a hybrid or cross-platform stack, the recommended approach is still to present the native Android SDK from the Android layer so you retain the same capture quality, permission handling, and behavior as a fully native app.