You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a passkey in Strongbox generates a series of fields within the KeePass entry. These fields do not have much value when accessing the login entry since the user very rarely (if never) will be copy pasting those values anywhere. This creates a very crowded details page within the entry that adds a lot of noise and makes finding the right information more difficult.
Suggestion
Easy Solution
I suggest the Passkey details are hidden behind a toggle the same way that the Metadata or the History hides information which is rarely accessed behind them.
Medium Solution
ProtonPass has a great implementation when displaying passkeys that is very attractive. I suggest looking into it.
The text was updated successfully, but these errors were encountered:
Hi @DannieBGoode - Thanks, could you attach a sample ProtonPass screenshot?
In the entry you can see there is a field called "Passkey" with the email of the account associated to that passkey. That entry is unlike the others because it is clickable.
If you click on it you get a popup with more details on the passkey.
The screenshots are taken on Desktop but it works exactly the same way on iOS.
P.D. For reference, on the first screenshot you can also see KPEX values created by Strongbox when I created a Passkey there (this login entry was later imported into ProtonPass), as you can see, all of these KPEX fields just add noise to the screen and are not useful so hiding them under a popup (or toggle) like Proton does seems like good UX.
Problem
Creating a passkey in Strongbox generates a series of fields within the KeePass entry. These fields do not have much value when accessing the login entry since the user very rarely (if never) will be copy pasting those values anywhere. This creates a very crowded details page within the entry that adds a lot of noise and makes finding the right information more difficult.
Suggestion
Easy Solution
I suggest the Passkey details are hidden behind a toggle the same way that the Metadata or the History hides information which is rarely accessed behind them.
Medium Solution
ProtonPass has a great implementation when displaying passkeys that is very attractive. I suggest looking into it.
The text was updated successfully, but these errors were encountered: