Tails

#3 Updated by tchou 2014-07-12 08:40:59

Hey !
I’m not shure if i’m on the right place, and maybe things should be split, butanyway, here it is :

Welcome to Tails screen

Language and keyboard

- When the user click the on/off button to remember the language and keyboard layout, a warning should pop-up for clear explanation of wich information may be leaked on the usb stick, with a clear button like “I’m OK with having in clear text my keybord and language setting on this Tails usb stick”.
- I’m wondering if we should add the “UTC time zone” option. Maybe 4 columns would be a lot on the screen but often user complains about having an enexpected time. Maybe we could add this configuration to the encrypted persitence and select it in the gnome environnement.

Unlock persistent data

- Change label to be more explicit : “Unlock your persistent encrypted data and preferences”

- I’m wondering what we should do when the user lunch Tails with a DVD.
- we could keep all the persistence possibily and pop-up that I need to copy its Tails into a usb stick
- or hide everthing because he can not at this moment performe the action
- I feel that the read-only option is used by no-one. If we want to keep it, we could have it in “Advanced configuration”

Guided configuration

navigation

- Add a “back” label for the back button

- We need to decide the differents way to go (or not) from one screen to another :
- click on the steps numbers
- click on items (like home & office)
- click on a “next” button

- Maybe we need to have labels on steps for each screen
- [1 - Tails ?] [2 - Context] [3 - Need to save ?] [4 - Check and go]
- We have to decide which is (and if there is) the default configuration for each screen
- maybe “public place” for step 2
- maybe “no” for step 3

screens

- screen 1 : Add a button at the bottom : “start the tour” or “next”

- screen 1 : Have the same title than the button you click on to arrive : “Guided configuration” (I think maybe on all screens)

- screen 2 : We need to work on the differents contexts, maybe add an “offline mode” that do not load any network modules.

- screen 3 : I wondering if you must use explicit label like “Yes, configure encrypted persistance” / “No, next step” and not just “yes” and “no”. Maybe it’s ok because it’s the only screen with this kind to label.
- screen 4 : “Go” button should be “lunch” (or at least, the same that we have in other screens)

Advanced options

- Have the same title than the button you click on to arrive : “Advanced configuration”

- I’m not shure we need password confirmation, but at least having a double field make this step a bit different from the persistence one. I think we need to have a quite clearely different UI for persistence and admin.
- I think configure persistent volume should be quite different from the other options, because you ahve to do something after. Maybe have a button, the same than on the Guided configuration “configure encrypted persistance”.

#4 Updated by intrigeri 2014-07-12 10:02:30

> I’m not shure if i’m on the right place, […]

The blueprint would be a better suited place for such information, IMO.

#5 Updated by sajolida 2014-07-13 07:58:09

> - I’m wondering if we should add the “UTC time zone” option. Maybe 4 columns would be a lot on the screen but often user complains about having an enexpected time. Maybe we could add this configuration to the encrypted persitence and select it in the gnome environnement.

I’m not in favor of having the timezone configuration stored in
persistence and configure directly from the clock on the desktop.

If there is no configuration in persistence we could try to “guess” the
timezone according to the local but it wouldn’t always work (for Russia
for example) so I’m not totally sure about that. Anyway, let’s not worry
about that now as we don’t have a configurable clock anyway.

> - I’m wondering what we should do when the user lunch Tails with a DVD.
> - we could keep all the persistence possibily and pop-up that I need to copy its Tails into a usb stick
> - or hide everthing because he can not at this moment performe the action

I’m in favor of either hiding those options. But then in the guided
configuration we can mention in step 3 that you need to run from USB in
order to save encrypted data.

> - I feel that the read-only option is used by no-one. If we want to keep it, we could have it in “Advanced configuration”

Good idea. I’m still not satisfied with the current design. I’m worried
that the On/Off switch for read-only might look like a switch for the
persistence or something…

> h2. Guided configuration
>
> h3. navigation
> - We need to decide the differents way to go (or not) from one screen to another :
> - click on the steps numbers
> - click on items (like home & office)
> - click on a “next” button

I think we said clicking on one of the buttons was enough to go from one
screen to the other. You can always rollback with the “back” button.

> - Maybe we need to have labels on steps for each screen
> - [1 - Tails ?] [2 - Context] [3 - Need to save ?] [4 - Check and go]

Geoffrey was only mentioning “dots” at the bottom of the page, without
even a number. So I wouldn’t add titles.

> - We have to decide which is (and if there is) the default configuration for each screen
> - maybe “public place” for step 2
> - maybe “no” for step 3

I don’t think so. The user needs to make a decision here and click on
one button or the other. If there is no “next” button, then there should
be no default.

> h3. screens
> - screen 1 : Add a button at the bottom : “start the tour” or “next”

I think the tour should be treated as a different task. It is good to
take this into consideration while revamping the Greeter but we don’t
have that content right-now. It will come later on, while reworking the
website I think.

> - screen 3 : I wondering if you must use explicit label like “Yes, configure encrypted persistance” / “No, next step” and not just “yes” and “no”. Maybe it’s ok because it’s the only screen with this kind to label.

Yes/No buttons have to be avoided and we should rather use explicit
buttons with verbs. So I’d say “Configure persistence” and “Start
without persistence”.

> h2. Advanced options
> - I’m not shure we need password confirmation, but at least having a double field make this step a bit different from the persistence one. I think we need to have a quite clearely different UI for persistence and admin.

We need password confirmation as this option is used to set a password.

> - I think configure persistent volume should be quite different from the other options, because you ahve to do something after. Maybe have a button, the same than on the Guided configuration “configure encrypted persistance”.

Agreed.

#6 Updated by alant 2014-07-17 12:08:07

Please discuss these issues in the dedicated threads on the tails-ux@boum.org mailing list (https://mailman.boum.org/listinfo/tails-ux).

#11 Updated by sajolida 2014-11-07 11:44:22

Done see https://mailman.boum.org/pipermail/tails-ux/2014-October/000092.html