UX meeting 20190815

Attended: @ninavizz, @redshiftzero, @harris, @eloquence, @huertanix, @emickll

Agenda

• Present: Rev2 things for 1.0.0, against our Source UI design principles...
  • Get Codename page + codename widget updates?
• Check-in: SD 1.0 UI Rev2 (erik)
  • FYI: Logo updates are happening; this guidelines doc was reviewed

Notes

Get Codename Page/Widget Updates

• See linx above
• Mickael flagged weirdness of old colors used in Get Codename page and confirmation messaging, in a PR review... which prompted Nina to present these past mockups to Erik as an option to consider squeezing into 1.0.0
• Overall
  • David: Journalists in on-sites cite that sources often re-submit under different names. What can be done to address that? Also, over-the-shoulder considerations?
  • Nina: Great question! The mental models w/ the whole "Codename" concept are also a bucket of unknown vaguesauce, and with what you just cited, all of this needs to be evalutated in a proper design and user research effort at a later date. This stuff here is only to make superficial tweeks for Erik to implement tomorrow.
  • Mickael: What about on the confirmation page—maybe just tweak that messaging?
  • Erik: Yep, the whole experience needs to be reconsidered, and that is totally a proper project effort. This review is to consider a "What can Erik do that won't be controversial or add to UI churn?" update.
• Different icon?
  • Lock is problematic because it speaks to abstract concepts of security—not specifically a codename.
  • Keyhole presented as Nina/Erik endorsed 'it sucks less than the lock' option
  • Harris: A key might be more intuitive? What about the word "Password" instead of "Codename"?
  • Nina: Key was presented in Feb and pushed back on for potential GPG confusion
  • Erik: I just reviewed history, and you're confusing that with the fingerprint
  • Consenssus: Stick with non-controversial changes; keep the lock, seek to update w/ user research informing decisions, at a later date.
• Action items:
  • Yes: go with color schema updates, slight layout design updates, re-ordering of text; keep the lock.