How rhyvex-the-dev/xenonypt works
Xenonypt is a cross-platform encrypted file-vault app. The user creates or unlocks a vault, manages encrypted files, and can extract or stream their contents; the Flutter UI communicates with the Rust vault core through flutter_rust_bridge. The graph preserves documented file-management, loose-file, streaming, obfuscation, and hardware-biometric capabilities. Source excerpts show the Rust API-to-vault calls and filesystem operations; Flutter UI behavior and biometric implementation details are documented only at a high level, so those links are marked unverified.
Main entry points: main.dart Vault UI · vault.rs File management · rust Dart bindings · frb_generated.rs Generated bridge
Components 13
Flutter app
- Vault UI
lib/main.dart
Rust bridge
- Dart bindings
lib/src/rust - Generated bridge
lib/src/frb_generated.rs - Vault API
lib/src/api.rs
Vault operations
- Vault core
lib/src/vault.rs - File management
lib/src/vault.rs - Encrypted metadata
lib/src/vault.rs - Chunk streaming
lib/src/vault.rs - Vault files
Device security
- Hardware biometrics
android/app/src/main - iOS Keychain
ios/Runner
Other components
- Vault user
- OS authenticator
Connections 12
- Vault user → Vault UI: uses
- Vault UI → Dart bindings: requests vault actions
- Dart bindings → Generated bridge: invokes
- Generated bridge → Vault API: dispatches calls
lib/src/frb_generated.rs - Vault API → Vault core: delegates to
lib/src/api.rs - Vault core → File management: performs
lib/src/vault.rs - File management → Vault files: reads and writes
lib/src/vault.rs - File management → Encrypted metadata: updates
lib/src/vault.rs - Chunk streaming → Vault files: reads chunks
- Vault UI → Hardware biometrics: requests biometric unlock
- Hardware biometrics → OS authenticator: authenticates with
- iOS Keychain → OS authenticator: uses biometrics