Re: [Tails-ux] Revamped greeter preview ISO available

Apologies for my hiatus! I had something urgent to attend to. I'll try to work my way backward as needed from this message.

Have you seen how 1Password does this? You type into the form analogous to the 3rd screenshot of yours, below. It has only a lock on it. When you finish typing the password and press Enter, the lock animates and moves across the field, unlocking itself like a little zipper or something.

Now that I see the four designs I'm quite worried that the lock and the word, when on the same button, are sending conflicting signals. For that reason I also prefer 2 and 4. I think 3 could work fine if we took the word off the button as 1Password does. (I'm counting the files from the top down.)

Contrast looks great!

I like "passphrase" because it suggests making a long one.

I am hopeful that user testing can discover whether the unlocked encrypted paradox is a problem. Maybe if you called it an encrypted container, your mental model would propagate. "Persistent storage" is accurate but not very evocative.

I hope my mail won't shrink this screenshot but it's been bad lately about that.

Susan


On May 17, 2016, at 1:44 PM, sajolida <sajolida@???> wrote:

> Susan:
>> I agree that the lock should show the state.
>
> I'm attaching to this mail four new mockups. I made them with Glade, the
> software to create Gtk interfaces, so they use the actual widgets,
> colors, fonts, etc. Still, It was my first time with Glade and I had
> problems with images so for example the (?) link is smaller than what it
> should be.
>
> Susan: do you think that this is enough in terms of contrast or do you
> still think that we should do something different that what's provided
> by Gtk by default? Like using bold as you suggested.
>
>> I suggest testing by asking users to explain whether it is locked or
>> unlocked to make sure there isn't any ambiguity. "What will happen
>> when you press that button?"
>>
>> My earlier comment about encrypted storage being locked or unlocked
>> is In regard to the technically naive concept of encrypted = locked.
>> So an unlocked encrypted container might not make much sense for some
>> people.
>
> I understand what you mean here and I never thought about it this way
> before, so sharing your mental model is very precious. The way I see it
> is is more like a treasure chest with a lock on it:
>
> http://vignette1.wikia.nocookie.net/clubpenguin/images/4/4b/Treasure_Chest_Costume_icon.png/revision/latest/scale-to-width-down/500?cb=20120517150232
>
> When you unlock the chest, you can access the treasure (the data) but
> the treasure is still in the chest. Here, when you unlock the encrypted
> storage, the data is not really decrypted (as in "copied elsewhere in a
> decrypted form"): it's still encrypted on the USB stick but you can
> access it while Tails is running because you opened the lock.
>
> So for example, I don't think we want the user to believe that their
> data has been decrypted. And we thought that the lock metaphor would
> help. But maybe there are things that could be improved to transmit this
> better.
>
>> However, I prefer the alternative you chose of putting the lock state
>> on the button with the text label, provided it tests well with users.
>> If it is confusing, then moving the lock off the button would be the
>> next thing to try.
>>
>> The lock by itself on the button would be ambiguous, but next to that
>> strong label I think it could work. Testing it with users is the only
>> way to be sure.
>
> As you can see, in the new mockups I tried both: having the icon inside
> and outside the buttons. The "inside" version looks nicer but the
> "outside" version is probably less ambiguous.
>
> I also made the labels of the buttons shorter because I don't think that
> the longer version is helping here.
>
> Spencer, would you be up to printing these and testing them quickly with
> different people?
> <relock inside.png><relock outside.png><unlock inside.png><unlock outside.png>_______________________________________________
> Tails-ux mailing list
> Tails-ux@???
> https://mailman.boum.org/listinfo/tails-ux