UX meeting 20190314

@ninavizz, Allie, John, David, @redshiftzero, @eloquence, Harris, @heartsucker

Design Review: Hey, hey, it's some VisDe! (for the Workstation Client)

Jen:
- Likes blue palette of sd.org
- Of the 4 shown today, likes Peter the most
- Likes SD logo same size as other hexagons
- Hexagons and logo(s) can be smaller/more-condensed
Erik:
- Agrees with Jen on all her points
- Doesn't have to be color intensity 1:1 as the website, which is too intense for looking at all the time
- Whatever color scheme we use for the logo should be more or less consistent with visual identity guidelines that are inevitably published; good to use this exercise as an opportunity to set future brand precedent.
- Mickey is too light; more "punch" sought.
- Likes that Peter fades at the bottom.
David:
- Journalists are heavy Microsoft users, so will be looking at those kinds of apps all day long
- Journos used to sparse apps
Action Items:
- Nina to iterate asap and push updates to folks by COB Friday
- Focus on a more literal interpretation of hexagons/branding from website
- Balance sizing of logo/hexagons to something between Peter and Mickey
  - More punch, but be mindful to not make it too busy
  - Doesn't need to be as intense as the website, but more punch is sought

Design Review: Reply A + Reply B, and segue'ing into Auth Widget pending network tasks message

Reply
- Contextual messaging = TMI
- No "Cancel" after hitting "Send"
- Network Activity Indicator with a companion log window for active/completed things will be important
  - "Stuff is happening" = appropriate level of detail for beta
- Show the spinner, no contextual progres status; network activity indicator plus spinner, no unique confirmation message.
- Message failures: client will continually try to do until hitting some designated failure point
- Retry/cancel makes more sense than Retry/Delete, per automated retries
Auth Widget related things
- Users unlikely to click "Sign Out"
- More probable pattern will be clicking VM window "x" at which time a dialog will need to appear to warn of pending tasks; but current details in Sign Out message too granular
- Post-force-shut notification not possible

Meeting (60min) Agenda:

Design Review:
- Workstation Client visual design review
- Workstation Client Reply: Which one of three options?
  - Option A ...uses footprint of Compose box to show progress.
  - Option B ...frees Compose box for user to compose a new message, while using paradigm explored in last week's Briefcase rev for contextual status messaging.
  - Option C = Option B, but with multiple concurrent messages sending
Discuss:
- Next sprint UX priorities?
  - Maybe a little love for the Source experience? 😃
    - Allie's suggestion to add "View/Hide" eye icon into Source login!
- Nina: Ask Jen for further clarification on Client "file downloaded, but decryption failed" issue
  - Unsure if: would a stored version of the encrypted file be kept on the Workstation machine, or would someone need to re-download the file after the key issue is fixed on the server or workstation? A little more clarity wd help. 😬
Shoutouts: Allie rockin' with progress on implementing Workstation UX into Client code!