Skip to main content
The Connect Android SDK handles passkey ceremonies through Android Credential Manager. Your existing backend remains responsible for account eligibility and application sessions.
1

Install

Use Android API level 26 or later and enable mavenCentral() in your dependency repositories.
Dependencies are resolved from published packages. See Maven Central for available versions.
2

Configure the app and backend

Follow native RP ID configuration to associate your app with the relying party through Digital Asset Links.Implement backend support for Connect tokens and signed-passkey verification. Do not put Backend API keys in the app.
3

Initialize

Create one instance with the application context and reuse it. Login, enrollment and management calls take the current Activity as a separate argument. Use your project’s frontend API suffix if it differs.
4

Implement the SDK flows

Follow the native integration guide for enrollment, login, fallback and management. Connect tokens come from your backend; passkey login results return to it for verification before a session is issued.

Verify

Test on a supported device with a configured credential provider. Check RP ID association, enrollment, successful login, cancellation, fallback and passkey deletion. See Android testing. The SDK source and example app show native API usage.