Improve user expectations management w/ "Export"

[ninavizz]

Problem

When going to export a file, I consistently observed this screen appear to freeze for 9 seconds, upon hitting submit on the passphrase for my drive. No presence of an active-state on the "Submit" button, and no confirmation that my passphrase was accepted (or being told my file is now saving to the drive), are why.

Solution

1. There needs to be an active-state on the buttons throughout Print and Export.
2. Users need some indication that a passphrase was accepted or not.
3. Users also expect some indication that the machine has moved past authenticating their drive, and is actively doing the task (in this case, saving a file to a drive).

9 seconds is a lifetime to users to see, literally, nothing.

While a confirmation screen does state that the export was successful, it concerns me that 9-seconds of nothing followed by a confirmation message, will still feel disconcerting. Especially when our users are not able to just go to a regular machine to verify the file transferred ok, and engaging an admin is required for that.

[eloquence]

Flagging for discussion, can be done asynchronously: Is this something Nick can realistically help with, or can changes to those dialogs only be tested effectively in Qubes? If Nick can't help with it, I'm afraid further improvements in this area will have to wait until all release blockers are resolved, i.e. almost certainly until after the first official beta release.

[ninavizz]

@eloquence I'm creating separate tickets for the two identified action-items this ticket identifies—the active state on print/export buttons, and the additional screen state. Art assets for both will be included in each.

[eloquence]

During QA, I'm noticing that this is particularly problematic when the user enters an incorrect passphrase, because the dialog will remain in this error state while successfully exporting:

[ninavizz]

From today's UX meeting, I've assembled the below.

Note, that none of the below is qualified by timing around beta, and is instead a general prioritization based on conversation around how today's experience works, abreast ideas expressed in this pdf.

Must

• Add an "Active State" to all primary buttons after the "Speedbump" screen.
• Speedbump Screen
  • Separate single screen into 2 distinct states: "Preparing" vs "Ready"
    • For Preparing
      • H1 text to say 'Preparing to [print or export]'
      • Spinner at top-left instead of device icon
      • 'Continue' button is disabled
    • For Ready
      • H1 text to say Ready to [print or export]
      • Show device icon in place of spinner at top-left of screen
      • Enabled "Continue" button
• Disable Password field when actively submitting pane for auths

Should

• Near-term option steps to remediate Pane Sandwich issue
• Update H1 texts with each state, as shown in PDF
• If "Could" cannot be done, use backup text edits to improve human-tone of text

Could

• Rejigger layouts of Icon, H1, and Byline, to accommodate improved error message placement and subsequent tone/voice
  • Smaller icons
  • No more HR
  • Uniform pane size and slight layout tweeks, to accommodate
  • Update content to reflect new hierarchies
• Include error-icon
• Include success icon

Won't (but wd be nice to do later)

• Include spot for stack-trace messages, beneath human writing for immediate user
  • Nice to include these for admins to see in shared Signal pix
• Kill HR on Speedbump screen, and rejigger text layout to have blue background as PDF shows, instead.

[ninavizz]

In the original comment, items n°2 and n°3 are unlikely to be addressed for the Beta release, but action items discussed in today's UX meeting and in the 3 child issues to this, should make a marked improvement. :)

[ninavizz]

All spinner art is in child issues, here. :D

[sssoleileraaa]

1. There needs to be an active-state on the buttons throughout Print and Export.

This was added today.

2. Users need some indication that a passphrase was accepted or not.

We've been showing the message "The passphrase provided did not work. Please try again." if the passphrase is not accepted and the "Export successful" screen if it is accepted. This paired with the change in #1 meets this criteria.

3. Users also expect some indication that the machine has moved past authenticating their drive, and is actively doing the task (in this case, saving a file to a drive).

This should be tracked separately because I think it needs ux discussion.

I think this is ready to be closed.

[zenmonkeykstop]

Fixed for export with wizard changes, will fix for print separately.