Threads: V2

The Threads MVP has been launched, this issue discusses items that are above and beyond the first release of Threads across platforms.

This issue does not yet have a definition of done. It's definition is dependent on the MVP launch of Threads.

For a full list of issues that have been moved to Post Launch, see here: https://github.com/orgs/vector-im/projects/17/views/37

**Before actioning this Initative we should review all the ideas captured below and apply Product thinking to them**
This is currently just a bit of a dumping ground so nothing gets lost.

---

### Issues not in the MVP of Threads:

#### Product

- \[ \] Short press on Mobile [WIP](https://docs.google.com/document/d/1pmB_tvslngZssWgHuuGtNZ0G6UBrGv9Rb3zu4cFJvCs/edit?usp=sharing)
- \[ \] Gracefully handling room upgrades [🗒️ Notes](https://github.com/vector-im/element-meta/issues/61#issuecomment-1014629516)
- \[ \] https://github.com/vector-im/element-meta/issues/118
- \[ \] Improved rendering of content types and formatting styles in threads \(root messages, thread summaries\). https://github.com/vector-im/element-meta/issues/121
Note: For the first release we've just normalized the behavior for all platforms taking the web implementation as the reference, even if not optimal \(e.g., spoilers aren't hidden, making everything plain text and getting rid of all styling, no icons for media, etc.\). An improved rendering would mean redefining what is the expected output for each content type and formatting style for a better experience.
- \[ \] Improved thread activity updates in room list [Exploration: Room list](https://www.figma.com/file/T309ztx0sNyOOK6NKVLHsK/Threads?node-id=3586%3A328211). **TODO**: Jano to add mockups for users who keep Previews off.
- \[ \] Consider other improvements and feature ideas [documented on GitLab](https://gitlab.matrix.org/new-vector/internal/-/wikis/Teams/Project:-Threads)

#### Web

- \[x\] https://github.com/vector-im/element-web/issues/19686
- \[ \] https://github.com/vector-im/element-web/issues/19361
- \[x\] https://github.com/vector-im/element-web/issues/19660
- \[ \] https://github.com/vector-im/element-web/issues/19713
- \[ \] Add some motion/transition when navigating back and forth between the thread list and a single threads, to reinforce the navigation path.

#### Android

- \[ \] https://github.com/vector-im/element-android/issues/4458 \(needs review\)
- \[ \] https://github.com/vector-im/element-android/issues/4460

#### iOS

- \[ \] https://github.com/vector-im/element-ios/issues/5140 \(needs review\)
- \[ \] https://github.com/vector-im/element-ios/issues/5142

---

#### Issues optimistically included in the MVP but might be pushed to V2...

- \[x\] https://github.com/vector-im/element-web/issues/19578

Review the remaining ideas in this issue, the linked project view, and the referenced Element Web, Android, and iOS issues. Begin with the requested product review and platform-specific context; this issue is not ready to action until the ideas are scoped and a definition of done is established.

Written by the indexing model from the issue text.