Skip to content

Feature: LHN, avatar and header updates to reports, workspace chats and chat rooms tied to workspaces. #20486

Closed

Description

@JmillsExpensify

While we recently implemented threads, tasks, and manual requests, we realized that threads followed one set of design patterns, while manual requests and tasks followed a different set of patterns. In an effort to clean this up for manual requests and IOUs – threads are already being implemented and tasks are being handled separately – this doc outlines a new, unified approach to ensure business use cases match the rest of the app.

LHN & Avatars
Screenshot 2023-06-08 at 21 18 23

Notes for completeness:

  • The workspace chat now uses a consistent avatar for members and admins, with the overarching goal being consistency and less confusion. Workspace chats use a 40x40 dual-avatar, with a larger workspace avatar and a smaller member avatar overlaid in the bottom-right. That said, the name of the workspace chat will continue to differ for admins, taking the form %memberName%, so that they’re able to find workspace chats for specific employees.
  • Expense reports use a 24x24 dual-avatar, with the rounded member avatar in the top-left and a rounded square workspace avatar in the bottom right. This dual avatar emphasizes the collaboration and shared nature of sending a request and eventually getting paid back. The title takes the form “%workspaceName% owes %amount%” (and updates to %workspaceName paid %amount% when settled).
  • IOU reports will similarly use a 24x24 dual-avatar, though both members have a rounded avatar in contrast. The title is the same as expense reports.
  • Requests made to the workspace will feature a larger 32x32 rounded member avatar, as well as a smaller 20x20 rounded square workspace avatar in the case of expense requests. The workspace overlay helps distinguish requests to a workspace vs a DM, which has no extra overlay. The title takes the form “%amount% request for %merchant% | %comment%”.
  • Threads in workspace rooms/reports will use a distinct “overlay” avatar from requests. A larger 40x40 circular member avatar as well as a smaller 20x20 rounded square workspace avatar overlaid in the bottom right. This similarly helps distinguish workspace threads from DMs, and emphasizes the member who made the parent comment. The title of the thread is the parent comment.
  • Threads in DMs/GroupDMs will simply use the avatar of the parent message sender.
  • All chat rooms tied to workspaces will feature the workspace avatar. This deprecates the chair and similar icons for user-created rooms.

Headers
image

Notes for completeness:

  • For the first line, the avatars and header follow the same convention as the LHN.
  • For the second line, we use “From %parentChat% in %policyName%”.
  • The parent report is always hyperlinked, displayed in blue and can be clicked to return to the parent report.

*iou/expenseReport subheaders

  • Remove the To: and amount
  • reposition the Pay button
  • modify the pay button copy, so it includes the report amount. i.e Pay $50 with Expensify

Mobile (Old | New):
image

Desktop (Old | New):
image

Rollout Plan

  • Update the subheader and parent navigation on all report types (PR) - @chiragsalian
  • Update the avatars in all places they feature (LHN, Chat Headers, Report Previews) (GH) - @grgia
  • Update the iou/expenseReport header logic. - @grgia - (GH)
    • Remove the To: and amount
    • reposition the Pay button
    • modify the pay button copy, so it includes the report amount. i.e Pay $50 with Expensify
    • Add the "wide" reportTotal to the expanded scrollable header
  • Update the iou/expense request header logic. - @grgia (GH)
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01d3518465643567ea
  • Upwork Job ID: 1666939604347977728
  • Last Price Increase: 2023-06-08

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    NewFeatureSomething to build that is a new item.
    on Jun 8, 2023
  2. melvin-bot commented on Jun 8, 2023

    @melvin-bot

    Current assignees @JmillsExpensify and @trjExpensify are eligible for the NewFeature assigner, not assigning anyone new.

  3. melvin-bot commented on Jun 8, 2023

    @melvin-bot
  4. melvin-bot commented on Jun 8, 2023

    @melvin-bot

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @s77rt (Internal)

  5. changed the title [-]Feature: LHN, avatar and header updates to IOU/Expenses, workspace chats and workspace chat rooms.[/-] [+]Feature: LHN, avatar and header updates to IOU/Expenses, workspace chats and chat rooms tied to workspaces.[/+] on Jun 8, 2023
  6. JmillsExpensify commented on Jun 9, 2023

    @JmillsExpensify
    ContributorAuthor

    Also @shawnborton did we decide one way or the other on all blue for the second line of the header rows? I still like the differentiated From but I think you had some doubts. Chime in now, because we're going to start implementing this soon!

  7. shawnborton commented on Jun 9, 2023

    @shawnborton
    Contributor

    I'm cool with leaving From in gray to differentiate it, I agree it does look a bit nicer.

  8. grgia commented on Jun 9, 2023

    @grgia
    Contributor

    @shawnborton are we good to combine this issue with #19264 ?

  9. trjExpensify commented on Jun 9, 2023

    @trjExpensify
    Contributor

    I'm cool with leaving From in gray to differentiate it, I agree it does look a bit nicer.

    I agree. @chiragsalian, want to add that as a commit to your PR before it gets reviewed and merged?

  10. 40 remaining items

  11. grgia commented on Jul 10, 2023

    @grgia
    Contributor

    are we moving the pin action into that overflow menu here, yeah? I believe that was the intention, in which case we should add it as a menu item within both the expense/iouReport view and request view.

    @trjExpensify why not just show the pin icon instead of the three dots?

  12. shawnborton commented on Jul 10, 2023

    @shawnborton
    Contributor

    Yeah, the intention was to move the pin action into the overflow menu. I like keeping things consistent and training the user that on basically every type of view (chat, task, expense, report, etc) you have an overflow menu that has additional options. So even if the pin is the only option available in some cases, I do like keeping things consistent by using the overflow menu.

  13. grgia commented on Jul 10, 2023

    @grgia
    Contributor

    I have both PRs MVP done for these two views. @shawnborton @trjExpensify could we sync up and make sure I'm not missing any steps in these PRs? (Note: I still need to clean code up)

    the intention was to move the pin action into the overflow menu

    Is there a separate issue or design doc section for the pin changes?

    Report
    #22484

    Request
    #22562

  14. shawnborton commented on Jul 10, 2023

    @shawnborton
    Contributor

    I think we missed putting this into an issue or design doc. That being said, happy to sync up and make sure we're all on the same page!

  15. shawnborton commented on Jul 10, 2023

    @shawnborton
    Contributor

    But yeah, the idea is that we basically give every top chat header (the thing with the avatar + user/room/task/expense/report name) an overflow menu. The pin icon will live behind the overflow menu, and sometimes we'll also have a call icon, a delete icon, etc.

  16. grgia commented on Jul 11, 2023

    @grgia
    Contributor

    EOD Update:

    Major PRs Ready For Review:
    🟢 Match LHN Avatars to Header Avatars #22467
    🟢 Expense Report Headers #22484
    🟢 Expense Request Headers #22562

    Follow-Up Issues I will be tackling separately as they affect more views: (Note, I may make some of these external)
    🟡 Move Pin Logic into Context Menu - #22635
    🟡 Update DropDown button style - #22540
    🟡 Update Header Link Style - #22641

  17. melvin-bot commented on Aug 3, 2023

    @melvin-bot

    This issue has not been updated in over 15 days. @JmillsExpensify, @trjExpensify, @s77rt, @grgia eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  18. trjExpensify commented on Aug 7, 2023

    @trjExpensify
    Contributor

    I think this should be back on weekly until we can close it out.

  19. JmillsExpensify commented on Aug 10, 2023

    @JmillsExpensify
    ContributorAuthor

    Yeah, agreed. We're down to clean-up now.

  20. JmillsExpensify commented on Aug 22, 2023

    @JmillsExpensify
    ContributorAuthor

    Given that we have an issue for everything that remains from here, and related because all those are already included in the wave3 project, I'm inclined to close this larger issue out. In fact, I'm going to go ahead and do that, though please re-open if I'm missing something.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

InternalRequires API changes or must be handled by Expensify staffNewFeatureSomething to build that is a new item.ReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions