Skip to main content
com.corbado:observe records native authentication telemetry. Your existing authentication code remains responsible for credentials, method execution and sessions. Early access: the Kotlin API can change between minor releases.
1

Install

Use Android API level 23 or later and enable mavenCentral() in your dependency repositories.
See Maven Central for published versions.
2

Initialize explicitly

Keep the nullable tracker in your app. Initialization can return null; authentication should continue independently. No Observe API key is needed in the app.
3

Report flow boundaries

When the login screen becomes visible:
After your identity system confirms a successful login:
Instrument method attempts between those boundaries with typed operation helpers. See the shared event model.

Native capture boundaries

The SDK provides optional autofill observation and operation helpers for credential ceremonies. Your application supplies screen and flow semantics; native capture does not infer the entire login journey. Web-based login components can use Autocapture.

Runtime controls and verification

Stopping transport alone still allows collection. Configure both controls according to your application’s requirements. The SDK batches delivery and can recover queued events after process restart. The library manifest includes INTERNET for transport and USE_BIOMETRIC for capability checks. These are normal Android permissions and do not present a runtime permission dialog. Verify failed attempts, method switches and the eventual outcome in Observe. See verification.