[f-1] Audit and update all Chat UI's and invite notifications

[NickTooker]

High level problem:

Currently, our invite notifications don’t really follow a cohesive pattern. There are many ways to invite people and then even more emails/notifications that are sent as a result of adding/updating users to workspaces, UCRs, invoice rooms and so on. We need to do an audit of all that messaging and update/standardize it all so:

• The messages look great and contains 0 bugs
• The text of the messages is updated and standardized.
• We make these messages look closer to product notifications than to our current plain text.

[maddylewis]

• Tracking Sheet - HERE
• More Details - HERE
• Slack Thread - HERE
• P/S Draft - HERE

[maddylewis]

Alright, was able to "clear my plate" so to speak on a few things, so i will review the thread you posted last week, nick, and then start updating our tracking sheet.

[maddylewis]

moving to daily to focus on this week

[NickTooker]

I am getting no invite at all when adding myself via mention to a new room.

[NickTooker]

Started a DOC to keep track of screenshots for styling in later phases!

[NickTooker]

P/S sent to strategy@ cc: @maddylewis

[maddylewis]

• Nick + Marketing Team QA'ing to gather the varying messages
• Once the QA phase is complete, Nick will call me back in to help with the copy and links and such!

[NickTooker]

Planning out a pre-design to decide what needs to be QA'ed.

[NickTooker]

@danielrvidal and I are still working through finalizing the pre-design that will go out this week.

[danielrvidal]

@NickTooker can you update this one when you get a chance.

[NickTooker]

Earnings and a few launches this week are taking priority but I will be writing up a recap to the pre-design tomorrow and we will move forward with the HL design doc at the end of the week.

[NickTooker]

LATEST DISCUSSION HERE.

[NickTooker]

LATEST DISCUSSION HERE.

[NickTooker]

Working through the roomDescription Design Doc first before returning to this initiative.

[NickTooker]

The latest update is that we have pivoted from our original goal through this discussion.

First, we'd like to fill out THIS DOCUMENT to get all of our Chat UI components and rules agreed upon. From there, we can move forward with a UI update, and then this GH which pertains to the notifications that the UI update will inform.

[NickTooker]

No change since my last update above, we are still working through the best next steps in the thread referenced, along with the rules and UI/email components within the document I've referenced.

[NickTooker]

@danielrvidal is going to lead up this initiative while I am OOO:

Here is the thread we are working from. Here is the GH where we originally asked @shawnborton to create mock-ups for roomDescriptions. Here is the design doc for updating roomDescriptions that we can transform into the all encompassing design doc for UI of Chat/Notifications. Here is the Components and Rules document that David created outlining how Chat UI / Notifications ideally work.

[danielrvidal]

Still working away on this. I've been prioritizing some Stage3/CVP/GBTA related things so this will have to come next week.

[danielrvidal]

Still working on this.

[danielrvidal]

Trying to come back to this sometime this week.

[danielrvidal]

Still on hold.

[danielrvidal]

We're now a/b testing the updated version: https://github.com/Expensify/App/issues/47108

[danielrvidal]

Still working on the A/B test. We're just waiting on the F1 room to open.

[danielrvidal]

Still waiting on a/b testing linked above. So this will be on hold. Moving to monthly to keep it open but no update needed for a while.

[trjExpensify]

You moving this into f1 project, Dan?

[danielrvidal]

Yea, I just updated to that project and will track it there.

[danielrvidal]

We're a/b testing the subject lines to start.

[danielrvidal]

This is still ongoing but not high priority.