Closed techninja1008 closed 1 month ago
Hmmmmmm. We have introduced an unencrypted UUID as part of quick unlock handling. We could "convert that into a color", but honestly I don't see this as useful in general. I think an unencrypted database name/summary would be fine and easy to introduce.
Sorry if I wasn’t clear - I was proposing the color to be a user configurable property. My motivation for it was from an accessibility standpoint: both I and a lot of the people close to me struggle with dyslexia, so having different colors makes it significantly easier to tell what we’re opening at-a-glance, without having to engage the part of the brain that deals with reading and understanding the text.
Summary
It would be very useful to visually distinguish different databases whilst locked, by having a combination of a short description ("lock screen summary") to state what the purpose is as well as a color label ("lock screen color") to visually distinguish different vaults at a glance.
Examples
Some basic GIMP visual mockups:
Context
Often when typing a long, secure password for a vault, it can be a nuisance when you type one for a different vault than the one you're unlocking (you've opened the wrong one, you're distracted etc) especially when you think you may have just typed it wrong. Providing a visual cue as well as a description helps for this, and is also generally useful for giving a slightly more meaningful description of the vault than what can fit safely in a file name.
Obviously, users need to consider that this feature would necessarily have to store the summary and color outside of the encryption layer of the vault, and the configuration UI would need to make this abundantly clear. Furthermore, an unencrypted description might not be appropriate for some users, who would prefer to use the existing "description" field. I believe that this still presents a useful improvement in UX for those who find it appropriate for their security model.
If this sort of feature is acceptable, I'm happy to investigate contributing it myself given a high-level overview of how you would want it implemented.