UX meeting 20190627

27 Jun 2019

Attending:

@ninavizz, @eloquence, @harrislapiroff, @redshiftzero, @creviera, @huertanix, @kushaldas

Discuss + Review:

• (10min) Quick Source UI check-in. Review SD#4535
• Next step priorities for Source UI beyond beyond #4500
  • What should be next? Review Nina's proposed priorities?

Been Readin' + Shoutouts:

• The Behavior Change Wheel - A guide to designing interventions
• Discussing Design - Getting ideas for how to structure design reviews to be more inclusive, productive (for all & for the product at large), and dare I say "fun."

---

• Nina:
  • Presents & review list here, abreast this InVision proto
  • Tor messaging deferred, to prioritize everything else & to focus on this stuff w/ Mickael present
• Kushal:
  • Curious about multi-file upload
• David:
  • Happy to see redundant buttons with "Submit" on them, addressed
  • Active state thing important; file uploads are soooo slow, especially on Tor
• Erik:
  • Active state requires JavaScript… heh.
  • (big discussion ensues… lots of sighs and no solution identified, other than warning users not to click “Submit” more than once)
• Multi-File Upload:
  • Browser native field for multi-file upload done as PR ~2yrs ago, but never merged
  • Linting issues making testing and maintaining a significant burden
  • Flask, Selenium issues also create maintenance burdens.
  • Given push towards 1.0, Jen resistant to explore until post-1.0, but is happy to explore after.
• Footer & Risk TLDR: -See Proto
  • Need to check with news orgs; to do after Micah's feedback. David, could you help with news org outreach for footer (D = yes!).
  • Erik has forwarded outreach example to David
  • Discussion to get more feedback on Your Safety TL;DR page draft & footer, from newsrooms.
  • Expressed desire to get some version of new footer design into the product for 1.0, ideally with put potentially w/o the Your Safety TL:DR page to link to.
• Logo change:
  • Needs to happen in 1.0 (Erik, Jen)
  • Nina to standardize/publish “official” version for use
    • Already done for Workstation, just need to pub to SD Repo
    • Q: Could we start a Styleguide in the SD Wiki to begin documenting ongoing frontend/design standards? A: Draft it in the UX repo, will move to SD repo once done.
• Ohai, testing?
  • Erik flags interest in doing inexpensive usertesting.com type testing
  • Usertesting.com and userfeel.com touched upon as options
  • Erik to inquire about budgeting w/ Trevor, Conor

Action Items + Decisions:

• Active State:
  • Decision: the problem of managing user expectations upon clicking the “Submit” button is real, but Javascript is required for the expected solution. Need to explore how to do w/o Javascript. Worst case, Nina can design a messaging workaround.
  • Action: Nina to create an issue in the SecureDrop repo, to either invite research on how to do the preferred solution, or to document the need for a design solution with messaging.
• Multi-File Upload:
  • Decision: Nina’s envisioned dreamscape solution would require Javascript, so the browser based version as demonstrated on this w3schools page was decided upon. A PR exists, but can’t get merged until 1.0 things completed.
    • Some CSS-only styling may be possible, but listing files selected by the user would require JS.
  • Action: Issue to get created, added to a post-1.0 sprint. Possible design update to side-by-side boxes, too?

• Get Codename page:
  • Decisions: Update buttons in near-term PR. No new translations required, button pairing already exists. No controversy.
• Languages dropdown
  • Decision: All agreed cleaned-up version nicer
  • Action: Nina to create issue in SD repo w/ art & Zeplin spec included; Erik to tag helpwanted
• #4500-01,02,03
  • Decision: Volunteer may or may not get to it, but it needs to get done for 1.0
  • Action: Erik to tag them helpwanted, aaaaaand Kushal asking a friend for help?
• Codename Reminder Widget
  • Decisions:
    • Soft agreement on moving it to the top, but wd need to happen with outline on Replies box—and preferable to do w/ UxR evidence backing up.
    • Redesign of widget itself still needs more work; testing to validate ideas
  • Action: Nina to create GH Issue that is not a priority to be acted upon
• Receive Replies
  • Decisions: Spoke more around, less to.
    • No pushback or dislike expressed for solution (minor text updates, outline around area where replies would appear)
  • Action: Nina to create GH Issue that is not a priority to be acted upon
• Icons Library Standardization
  • Decisions: Material.io is a go
    • Nina still shd do 1:1 comparison to outline rationale
  • General: Folks prefer the fontawesome team/roots, but were ok to leaving it to Nina. Nina also loves fontawesome story/roots, but wants to go with system developed with stronger design expertise and research backing it.
• Footer + Risk TL;DR
  • Micah yet to respond; Nina pinged again
  • Desire to get more newsroom folk to provide feedback
    • David agrees to poke friendlies, after Erik asks
  • Desire to get into 1.0, but may not happen
• Source User Testing
  • Desire to simply get randos walking through task of submitting a tip through an instance
  • Would also be nice to validate some proposed copy edits from InVision
  • Nina to create UX Repo ticket to draft a plan
  • Erik to do budgeting inquiries w/ TDawg

Action Items By Individual

• Nina
  • Punchlist Here
• Erik
  • Tag #4500-3 with “Help Wanted”
  • Tag immediately-actionable issues Nina agreed to create in SD Repo w/ “Help Wanted”
  • UxR budget chat w/ Trevor/Conor
• Kushal
  • Check w/ CSS luvin’ friend on interest in doing #4500-3
• David
  • Engage w/ peeps in other newsrooms to continue soliciting feedback on updated footer text and SD Risks TL;DR page.