Add context hint for profile passwords #39

New Issue

str4d · 2021-06-27T11:12:38Z

str4d commented

2021-06-27 11:12:38 +00:00

When creating a new profile, it isn't clear why a password should be set. The password box is ticked by default, but unticking it creates no observable UX change other than removing the password fields. In particular:

I don't know what the profile password actually protects / enforces.
I don't know whether a profile without a passphrase has any on-disk protections at all.
If I later go into the profile settings and add a password, what will happen then? Is there a downside to adding the password later rather than immediately?

Given there is so much available UX space when the password box is unticked, it would be helpful to explain what the user is losing from not adding a password, and what they can regain later in settings. Ideally the user would get some sort of hint in both toggled states.

When creating a new profile, it isn't clear why a password should be set. The password box is ticked by default, but unticking it creates no observable UX change other than removing the password fields. In particular: * I don't know what the profile password actually protects / enforces. * I don't know whether a profile without a passphrase has any on-disk protections at all. * If I later go into the profile settings and add a password, what will happen then? Is there a downside to adding the password later rather than immediately? Given there is so much available UX space when the password box is unticked, it would be helpful to explain what the user is losing from not adding a password, and what they can regain later in settings. Ideally the user would get some sort of hint in both toggled states.

👍 2

sarah added the

bug

label 2021-06-27 14:58:07 +00:00

sarah added this to the Cwtch Beta 1.1 project 2021-06-28 21:08:22 +00:00

schlink commented

2021-07-01 02:05:29 +00:00

Is the question of whether the user needs to set a password effectively simplified as "Do you trust all users of this device?"? Maybe that concept could help make the profile creation workflow easier to understand.