[Story] Improve DMs

[VolkerJunginger]

Story

This story lists task to improve the UX for DMs

1. Remove the following state events at the start of the timeline:

• "This is the beginning of [username]"
• You created the room
• You joined the room

2. Show the following state events

• Encryption enabled
• You invited [username]
• [username] accepted the invite

3. In the room details create a new string for "Leave room".

• A DMs should not be reffered to as a room but a conversation.
• Change action to "Leave conversation"

Leads

• Tech: @jmartinesp
• Design:

Dependencies

• TBD

Sign-offs

Android

• Design sign-off on completion
• QA sign-off on completion
• Product sign-off on completion

iOS

• Design sign-off on completion
• QA sign-off on completion
• Product sign-off on completion

Scope

Android

Preview Give feedback

1. Remove verbose state events from the timeline element-x-android#2216
   T-Task +1
   
2. Improve the initial timeline items for DMs element-x-android#2217
   T-Task +1
   
3. Change 'Leave room' in DMs to 'Leave conversation' element-x-android#2218
   T-Task +1
   

iOS

Preview Give feedback

1. Improve the initial timeline items in DMs element-x-ios#2329
   T-Task +1
2. Change 'Leave room' in DMs to 'Leave conversation' element-x-ios#2330
   T-Task +1
   

Rust

Preview Give feedback

1. timeline: Add TimelineEventTypeFilter matrix-org/matrix-rust-sdk#3025
   +0

Out of scope

We decided that the work on read receipts will be done in a broader epic to get them right. The following tasks will then happen later:
- element-hq/element-x-android#2311
- matrix-org/matrix-rust-sdk#3065

They have a dependency on the timeline cache we are going to do this quarter.

[jmartinesp]

About removing the 'this is the beginning of someone', there is also a version with 'this is the beginning of this conversation' that we could use for DMs if we wanted to. I'm just mentioning it in case this wasn't known.

Also, just to confirm: on Android we're displaying way more state events than those, including some placeholders for power levels, room join rules, etc., which we'll probably want to remove (I think iOS is already hiding them). Do we want to hide any events of this kind from the timeline, not only the initial ones?

[jmartinesp]

Also, should removing the initial:

"This is the beginning of [username]"
You created the room
You joined the room

Be done to all rooms, or just DMs? @VolkerJunginger

[VolkerJunginger]

About removing the 'this is the beginning of someone', there is also a version with 'this is the beginning of this conversation' that we could use for DMs if we wanted to. I'm just mentioning it in case this wasn't known.
Thanks, but I think this intro is not needed.

Also, just to confirm: on Android we're displaying way more state events than those, including some placeholders for power levels, room join rules, etc., which we'll probably want to remove (I think iOS is already hiding them). Do we want to hide any events of this kind from the timeline, not only the initial ones?

Yes, please! Thanks for pointing that out.

[VolkerJunginger]

Also, should removing the initial:

"This is the beginning of [username]"
You created the room
You joined the room

Be done to all rooms, or just DMs? @VolkerJunginger

no, for now just DMs.

[jmartinesp]

@VolkerJunginger I just realised we have this confirmation dialog too when leaving a room:

Should we also have an alternate message changing room to conversation here?

[VolkerJunginger]

Is this true? If I leave a DM I cannot rejoin?

[jmartinesp]

Is this true? If I leave a DM I cannot rejoin?

Not until you're invited again by the other user, trying to open a DM with them would create a new one.

But that wasn't what my question was about: we have several messages when leaving a room/DM and they all mention 'room' and not 'conversation'. Should we create alternative texts for all those?

When a room is private:

Are you sure that you want to leave this room? This room is not public and you won't be able to rejoin without an invite.

When a room will be empty after you leave:

Are you sure that you want to leave this room? You're the only person here. If you leave, no one will be able to join in the future, including you.

The generic one:

Are you sure that you want to leave the room?

[VolkerJunginger]

ok, that helps. Then we need an alternative for DMs. Given the info above I would go with this:

| "Are you sure to leave this conversation? You will only be able to rejoin when being invited by [username]"

Would that be possible?

[jmartinesp]

Sure, I just wanted to confirm that's what we wanted to do. I'll create alternative texts for all those in localazy and add to the tasks to do to use these new strings for DMs.

[jmartinesp]

@VolkerJunginger sorry, another question. We want to remove the 'You created the room' message, but does it mean for both the user that created the DM and the invited user? So the invited user wouldn't see 'Someone created the room' either? I think it's fine since the user will have to accept the invite and they should know they didn't create the room, but just double checking.

[VolkerJunginger]

No need to be sorry. You have way more info looking at the code that I do just looking at the apps - I appreciate you bringing these questions up.

Yes, remove for both users.

[Velin92]

@VolkerJunginger Opened up these two issues for having RRs only displayed on messages and not on state events, if you feel they should be included in a separate story/issue that needs to be specced out here they are:
element-hq/element-x-android#2311
matrix-org/matrix-rust-sdk#3065

[jmartinesp]

matrix-org/matrix-rust-sdk#3025 is now merged, but it needs to be implemented in the clients yet.

Be aware the API used for fullRoom() now requires you to first initialize the timeline:

if (!roomListItem.isTimelineInitialized()) {
    roomListItem.initTimeline(eventFilters) // or null/nil if you don't want to pass any filter
}
roomListItem.fullRoom()

The filters I've added myself are:

val eventFilters = TimelineEventTypeFilter.exclude(
    listOf(
        FilterStateEventType.ROOM_ALIASES,
        FilterStateEventType.ROOM_CANONICAL_ALIAS,
        FilterStateEventType.ROOM_GUEST_ACCESS,
        FilterStateEventType.ROOM_HISTORY_VISIBILITY,
        FilterStateEventType.ROOM_JOIN_RULES,
        FilterStateEventType.ROOM_PINNED_EVENTS,
        FilterStateEventType.ROOM_POWER_LEVELS,
        FilterStateEventType.ROOM_SERVER_ACL,
        FilterStateEventType.ROOM_TOMBSTONE,
        FilterStateEventType.SPACE_CHILD,
        FilterStateEventType.SPACE_PARENT,
        FilterStateEventType.POLICY_RULE_ROOM,
        FilterStateEventType.POLICY_RULE_SERVER,
        FilterStateEventType.POLICY_RULE_USER,
    ).map(FilterTimelineEventType::State)
)

[Velin92]

matrix-org/matrix-rust-sdk#3025 is now merged, but it needs to be implemented in the clients yet.

Be aware the API used for fullRoom() now requires you to first initialize the timeline:

if (!roomListItem.isTimelineInitialized()) {
    roomListItem.initTimeline(eventFilters) // or null/nil if you don't want to pass any filter
}
roomListItem.fullRoom()

The filters I've added myself are:

val eventFilters = TimelineEventTypeFilter.exclude(
    listOf(
        FilterStateEventType.ROOM_ALIASES,
        FilterStateEventType.ROOM_CANONICAL_ALIAS,
        FilterStateEventType.ROOM_GUEST_ACCESS,
        FilterStateEventType.ROOM_HISTORY_VISIBILITY,
        FilterStateEventType.ROOM_JOIN_RULES,
        FilterStateEventType.ROOM_PINNED_EVENTS,
        FilterStateEventType.ROOM_POWER_LEVELS,
        FilterStateEventType.ROOM_SERVER_ACL,
        FilterStateEventType.ROOM_TOMBSTONE,
        FilterStateEventType.SPACE_CHILD,
        FilterStateEventType.SPACE_PARENT,
        FilterStateEventType.POLICY_RULE_ROOM,
        FilterStateEventType.POLICY_RULE_SERVER,
        FilterStateEventType.POLICY_RULE_USER,
    ).map(FilterTimelineEventType::State)
)

Just opened a PR for it on El-X-iOS:
element-hq/element-x-ios#2404

[VolkerJunginger]

Please also update the localazy translations.