Dimillian / Dimillian/IceCubesApp
Feature request: Clearer threading for deep and varied threads
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 7.1k
- Forks
- 720
- PR merge metrics
- No merged PRs in 30d
Description
- I have searched for similar issues using the text "thread."
Summary
The simple representations of threads we have now can make it difficult for me to track the flow of the conversation. Threads are complicated structures, and the current representation of long and varied threads (10+ deep, 2+ wide) can be challenging to read. IceCubes has one of the better models, but it is often confusing and difficult to parse.
Suggestion
Unfortunately, I don't know what an "ideal" threading model would look like, but I hope we can use this as a jumping-off point. Some mechanism of more progressive disclosure (rather than immediately showing the entire conversation) would make the flow of conversation easier to follow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. Start by locating the current thread representation in the IceCubesApp SwiftUI client and review how deep and wide conversations are displayed. Done would require an agreed progressive-disclosure design and corresponding behavior for complex threads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100