feat(desktop): unlock by sliding the vault doors open - #19
Merged
Conversation
The locked app is one sealed surface with the dcrypt mark across the seam, which doubles as the loader while the key is derived; unlocking parts it to reveal the vault already rendered behind, and locking slides it shut.
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Unlocking is no longer a screen swap — it removes a physical barrier. The locked app is one sealed surface carrying the dcrypt mark across the seam; on unlock the surface splits down the middle and the halves slide off-screen, revealing the vault that was already rendered behind them. Locking runs it in reverse.
Three ideas make it work:
The mark tears in half for free. Each panel is
w-1/2 overflow-hiddenand contains a viewport-wide copy of the face, offset so the two copies compose one image:Sealed, it looks like one logo; parting, each door carries its own half.
The loader and the door are the same thing.
Loadergainedanimate, so the mark assembles itself while Argon2id runs (the real 1–2 s wait) and rests as the finished stack otherwise — no spinner-then-transition. The separate full-screen busy view inUnlockScreenis gone; it is now just the controls that ride on the doors.The vault is mounted before the doors move, which is what sells the reveal.
Appreplacesunlocked: booleanwith a phase:opening→unlockedandclosing→lockedare committed by the doors'onRest. Locking firesvault.lock()concurrently with the animation, which the earlier snapshot-key work made cheap enough to hide entirely behind 380 ms.Motion: 560 ms
cubic-bezier(.2,.8,.2,1)open (measured deceleration 0 → −800 px), 380 ms closing with a slight overshoot past centre so it reads as a latch (measured:−283 → +10.6 → 0), inner-edge shadows only while travelling, and the vault settlingscale(.985) → 1behind.prefers-reduced-motioncollapses all of it to a 120 ms cross-fade.Testing
Measured both directions in the running app over CDP (transform samples above, frames in the webps). Desktop lint, 27 tests (including new
doorDurationcoverage) and build pass.Link to Devin session: https://app.devin.ai/sessions/04636534e07048089ffb6b78142e12cd
Requested by: @pyramation