for the desktop app: otp codes should not be part of the otp field but should be shown at the top of an entry in detail display when unlocked. the time remaining should be a bar below the entry. this is like the TUI in a way, but of course use normal large fonts here.
for the desktop app: otp codes should not be part of the otp field but should be shown at the top of an entry in detail display when unlocked. the time remaining should be a bar below the entry. this is like the TUI in a way, but of course use normal large fonts here.
hugo
added this to the 03 - Cross-platform Iced desktop app milestone 2026-08-11 05:03:00 +00:00
hugo
changed title from show otp codes at top of entry details when unlocked to desktop app: show otp codes at top of entry details when unlocked2026-08-11 05:03:18 +00:00
The desktop viewer now presents the generated OTP once at the top of an unlocked entry, before all entry fields. TOTP codes use a 42-point grouped display with a countdown and progress bar driven by the storage-provided validity period; HOTP codes show their committed counter without a misleading timer. The raw OTP field retains its URI, metadata, and actions, but no longer duplicates the generated code. Entry changes and authentication loss clear the presentation, while the existing tick lifecycle updates and regenerates TOTP at expiry.
Verification:
cargo test --package ironstorage-desktop --offline (34 passed)
cargo test --workspace (including storage RFC OTP and desktop OTP boundary tests)
Implemented and pushed as d6bcbbe.
The desktop viewer now presents the generated OTP once at the top of an unlocked entry, before all entry fields. TOTP codes use a 42-point grouped display with a countdown and progress bar driven by the storage-provided validity period; HOTP codes show their committed counter without a misleading timer. The raw OTP field retains its URI, metadata, and actions, but no longer duplicates the generated code. Entry changes and authentication loss clear the presentation, while the existing tick lifecycle updates and regenerates TOTP at expiry.
Verification:
- cargo test --package ironstorage-desktop --offline (34 passed)
- cargo clippy --package ironstorage-desktop --all-targets --offline -- -D warnings
- cargo fmt --all -- --check
- RUSTFLAGS="-D warnings" cargo check --workspace --all-targets
- cargo clippy --workspace --all-targets -- -D warnings
- cargo test --workspace (including storage RFC OTP and desktop OTP boundary tests)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
for the desktop app: otp codes should not be part of the otp field but should be shown at the top of an entry in detail display when unlocked. the time remaining should be a bar below the entry. this is like the TUI in a way, but of course use normal large fonts here.
show otp codes at top of entry details when unlockedto desktop app: show otp codes at top of entry details when unlockedImplemented and pushed as
d6bcbbe.The desktop viewer now presents the generated OTP once at the top of an unlocked entry, before all entry fields. TOTP codes use a 42-point grouped display with a countdown and progress bar driven by the storage-provided validity period; HOTP codes show their committed counter without a misleading timer. The raw OTP field retains its URI, metadata, and actions, but no longer duplicates the generated code. Entry changes and authentication loss clear the presentation, while the existing tick lifecycle updates and regenerates TOTP at expiry.
Verification: