[Story] Threaded message decorator in EX

[manuroe]

Description

• As a user
• I want to know when a message is coming from a thread
• So that I can use the reply action to make my answer goes to a thread. It will not break the UX of other users with matrix clients supported threads

This is a cheap workaround before we implement threads in EX. We are aware that only matrix power users will understand that using the reply button will not break UX on thread-capable apps.

Acceptance criteria

• Visual indicator like 🧵 on threaded messages in the timeline
• The action menu must display "Reply in Thread"
• The composer should have the hint "Reply in Thread"
• Reply to such a message will appear in the thread on matrix apps that support threads (Element Web and legacy mobile apps). There is nothing to implement here. It is already working

Size estimate

S

Dependencies

• None

Preconditions

• None

Out of scope

• No change in the room list
• No change in push notifications
• Polls and Stickers decorations

Open questions

• None

Subtasks

Android

Beta Give feedback

1. Threaded message decorator in EX vector-im/element-x-android#1236
   A-Threads A-Timeline T-Enhancement Z-Schedule +4
   
2. Tap and hold anywhere in a threaded message bubble should bring up the bottom sheet vector-im/element-x-android#1423
   A-Threads A-Timeline O-Frequent S-Minor T-Defect Z-Schedule +6
   
3. When swiping right on a thread, the message should have a "Reply in thread" string vector-im/element-x-android#1422
   A-Threads T-Defect Z-Schedule +3

iOS

Beta Give feedback

1. Threaded messages Decorator vector-im/element-x-ios#1687
   A-Threads A-Timeline T-Enhancement Z-Schedule +4
   

Rust

Beta Give feedback

1. Information to indicate a timeline event is coming from a thread matrix-org/matrix-rust-sdk#2519
   A-Threads A-Timeline X-Needs-Rust Z-Schedule +4
   

• QA signoff on completion
• Design signoff on completion
• Product signoff on completion

[callumu]

I have a few questions:

1. When is the deadline for the design work on this needed?
2. Is changing the composer placeholder text or changing anything visually in the composer out of scope? I'm unsure if this follows 'change the composer behaviour'

[manuroe]

2. Is changing the composer placeholder text or changing anything visually in the composer out of scope? I'm unsure if this follows 'change the composer behaviour'

It is out of scope. UX will not be great. This is why I added warnings about only power users will know it. You can sync with @amshakal to understand the logic behind.

[Velin92]

As of right now the Rust SDK is only capable of checking if a Message Like Event is threaded or not.
These are the following event types that can be threaded:

case emote
case image
case audio
case video
case file
case notice
case text
case location

This means that Stickers and Polls are out of scope as of right now

[manuroe]

Thanks to the nice @callumu's input in figma, I removed the following from out of scope
Change the composer behavior or add specific actions to threaded messages. Only aware people will know that they can use the existing reply action to not break the thread

and added new acceptance criteria:

• The action menu must display "Reply in Thread"
• The composer should have the hint "Reply in Thread"

cc @ganfra @Velin92