azuma doa Flutter Example

azuma doa example is a reference client for the azuma DOA platform. It exists to show integrators how the device binding, passkey and biometric flows fit together, and to give the team a real client to test protocol changes against. It is a developer sample, not a product. It holds no patient data, performs no clinical function, and is not a medical device. WHAT IT DEMONSTRATES • Device binding — a hardware-backed key pair generated in the Android KeyStore, with key attestation proving to the backend that the private key cannot leave the device. • Username and password sign-in, where every request is signed by that device key. • Passkeys (FIDO2) — creating an account whose first credential is a passkey, linking a passkey to an existing account, and passwordless sign-in, all through Android Credential Manager. • Biometrics — an EC P-256 or RSA-3072 key held behind BiometricPrompt, used to link a biometric credential and to sign in with it. • Sign-in by account ID, and session token refresh. • A dashboard listing the profile, linked passkeys and linked biometric credentials, with unlink for each. REQUIREMENTS • Android 9 (API 28) or newer. • Passkey and biometric flows need a device with a screen lock and an enrolled biometric. • An account on the azuma test environment. This build talks to a test backend and is not connected to production data. DATA Credentials you enter are kept on the device in Android KeyStore-backed encrypted storage and are sent only to the azuma backend. The app contains no analytics, advertising or tracking components.