VaultState

Lifecycle of a process-wide SecureVault, surfaced as state your Compose UI is expected to render explicitly.

Why a state machine? Both Android (Keystore handshake) and iOS (Keychain cold start) can do tens to thousands of milliseconds of work the first time a vault is touched, and can fail terminally (e.g. Keystore wipe after a factory reset). Surfacing those as distinct UI states — rather than hiding them behind an optimistic "always Ready" view — is the difference between a polished app and one that races against itself on cold start.

Get one via rememberSecureVault; render via:

when (val s = state) {
    VaultState.Initializing -> SplashScreen()
    is VaultState.Failed    -> ErrorScreen(s.reason)
    is VaultState.Ready     -> ProvideSecureVault(s.vault) { HomeScreen() }
}

Inheritors