Re: [Tails-ux] Greeter mockups

Delete this message

Reply to this message
Autore: Alan
Data:  
To: tails-ux
Oggetto: Re: [Tails-ux] Greeter mockups
Hi!

On Tue, 03 Feb 2015 14:03:28 -0800
spencerone@??? wrote:
> I took a deeper look at the screens shared by Alan and had some thoughts
> about the underlying structure of the greeter, which, after digging into
> the existing flow here:
> https://tails.boum.org/blueprint/greeter_revamp_UI/, prompted me to
> explore my thoughts visually and share them here with you [attached].
>

Thanks for this very nice graphical thoughts. I find it quite clear.
One question thought: are B, C, D and E different exclusive options or
do they combine together somehow, and if yes, how?

> Though the attached proposal contains a few structural options, I think,
> ultimately, I am suggesting a simplification of the greeter by reducing
> the need to fork the Tails greeter flow only to when someone opts for a
> guided walkthrough/tour of the configuration settings or opts for no
> guided walkthrough/tour of the configuration settings.


I apologize if we weren't clear enough on that, but we're supposed to have
already validated the flow with UX people at NUMA and do some
paper testing sessions on that flow, so I'm a bit reluctant to go back
and have to go through these steps again. That doesn't mean there's no
room for improvements or new ideas, but I'd like to make clear that the
flow documented on the blueprint should be taken as a basis and that
I'll need strong argument to start from the beginning again.

> I am also
> suggesting a summary of all of the configuration settings, default or
> saved, upfront on the first dialog screen [Option D].
>

That sounds like a good idea to me to be more clear on what are the
defaults when one clicks "Start Tails" button. Have you seen that we
aleady have a similar screen when defaults are saved:
https://tails.boum.org/blueprint/greeter_revamp_UI/#index1h3.
In this case the 1st screen is already a "check and go" screen, which
is what I understand that you suggest in option C.

We could genelize that if we find a consize UI to show which advanced options
will be selected. Would that address your suggestion?

> Let me know what you think :)
>

About option B (walking every person though the entire settings): I
think it's not something we desire as one of the goals of the redesign
is to have an interface as straightforward as possible for simple
cases, and that most of the advanced options are very specific.

Thanks again for spending time on that, it's nice to see it raises some
interest!

Cheers