UX parity between prototypes & coded client

[ninavizz]

Related Issues from the UX Repo:
• Client Content Design/Inventory
» Table in first comment has full inventory list of icons w/ SVG art for completed ones.
» Cut-art for elsewhere in the Client chrome will be included in related task Issues
• Client Visual Design
• Client Interaction Design

---

»» Zeplin Project for this Issue ««

• Re-Factor Client Grid ([client styling] Refactor client grid layout #259)
• Apply Source Pane Styles
  • Within scope of features already implemented
  • Gradient details for background that spans this and the Messaging Pane, in its Styles Issue
  • No unique "Issue" for styling most of this, just follow Zeplin
• Apply Conversation Pane Styles ([client styling] Apply Conversation Pane styling #272)
  • Within scope of features already implemented
• Apply Reply Pane Styles ([client styling] Apply "Reply" pane styling #268)
  • Replace boring button w/ awesome airplane
• Apply Auth Widget Styles/Interaction(s) ([client styling] Create and place auth widget #264)
  • "interactions" within the scope of existing functionality = dropdown to signoff, vs static button
  • Placeholder initials and username instead of FName/LName, until Admin interface expanded to support FN/LN
• Apply Refresh Widget Styles/Interactions
  • Text styles for Refresh timestamp, in Zeplin mox
  • Static & Active icons, in Content Inventory (link above)
• Configure Qubes SVS VM window for Workstation (#260)
  • Make the window match the spec'd purple, spec'd stroke color, spec'd dropshadow
  • Spec icons style
  • Spec typeface for VM Name
  • Update VM naming convention for SVS to more user-friendly [SD Workstation]
  • Not in scope for current sprint... 😢

[ninavizz]

^ Updated above punch-list to reflect ID Badge implementation blockage flagged in SD-4251, and recommended workaround until the SD-4251 resolved.

Acceptance of this Epic is not dependent on the ID Badge thingy being unblocked. Just FYI! @creviera

[ninavizz]

^ @creviera BUMP! Added style tidbits on Refresh button, inline with text on OG comment. Created new issue for Auth Widget, which I'll be completing momentarily.

[ninavizz]

@creviera do you and @redshiftzero think there's enough from me between this Issue and the details provided in all the linked issues, for documentation/reference on this sprint's needs?

[eloquence]

Thanks for filing these, @ninavizz! I've added them to the board, replacing the placeholder cards, and to the spreadsheet. Per the current plan we still need to flesh out issues for :

• Apply Source Pane Styles
• Apply Messaging Pane Styles

Jen/Nina/Allie, please jump in if you think that breakdown no longer makes sense. :)

[ninavizz]

^ @creviera I refrained from creating unique Issues for the Source Pane Styles and the Messaging Pane Styles, figuring the screens in Zeplin should provide adequate guidance for a first pass. What do you think? Happy to create unique issues for those, if more info would help. 😃

[ninavizz]

Hey folks—I spaced on including the Login screen, in my list above—but recall discussing it with Erik and Allie, last Thursday. I also don't see an Issue for it—was one created that I suck at finding, @eloquence? Asking, cuz I wanted to know if for Beta we're still planning to do the combobox/dropdown for known usernames for a specific Client instance: https://invis.io/J3R7XDP2DSZ#/354546900_SignIn-Online

[eloquence]

Login UI changes are out of scope for the current sprint. For the next sprint, we may want to tackle the actionable changes identified in freedomofpress/securedrop-ux#48 (comment) as a narrowly scoped issue.

We've not decided whether we want to include the "list of users" for offline mode. I suspect that we may reach a point where it's easier to have that list than to suppress all state in offline mode. For this reason I would love to see a final design with the dropdown, but we'll likely not implement it immediately.

[ninavizz]

Dev-actionable things for the near-term need to be resolved in a solution that scales-out to what's desired for Beta... so what we identified as "actionable" for the UX Kid to work on in this sprint in prep for the Dev Kid to implement next sprint, the UX Kid still needs to consider as a minimization of what is the preferred solution for Beta. Hence, asking the prior question. 😸

I'm personally in favor of preserving the drop-down for offline mode, as I suspect it'd feel weird for users if it went away.

[ninavizz]

Ohai this issue is sooooo obsolete; much has changed, so, closing!