Mail/Threading/Comparative: Difference between revisions

Elenuzza (talk | contribs)
Elenuzza (talk | contribs)
Line 1: Line 1:
We have grouped some of the most used systems to understand their advantages and disadvantages and spark ideas on possible solutions to old problems.
We have grouped some of the most used systems to understand their advantages and disadvantages and spark ideas on possible solutions to old problems.


Email threading UI has undergone significant improvements in the past five years. Modern email clients now offer more intuitive and visually appealing thread displays, with clearer hierarchies and improved readability. A notable advancement is the shift towards displaying newer emails at the top of threads, aligning with the chronological order of timelines and matching users' natural reading patterns.  
According to my understanding, there have been good advancements in UI design for email threading in the last years, particularly the significant improvement of displaying newer emails at the top of threads. This approach now aligns more intuitively with users' natural reading patterns and chronological expectations.  


Here a quick threading overview of some of the most used software
Here a quick threading overview of some of the most used software
Line 14: Line 14:
* Thunderbird does not currently offer an option to sort conversations in reverse order within a thread
* Thunderbird does not currently offer an option to sort conversations in reverse order within a thread


The subject seems to appear on all messages under the same thread. I'm asking myself whether it is necessary or if it clutters the space without much point.  
The '''subject''' seems to '''appear on all messages under the same thread'''. I'm asking myself whether it is necessary or if '''it clutters the space''' without much point.  


== Outlook ==
== Gmail (Windows desktop app) ==
[[File:Gmail.jpg|alt=Gmail Threading|thumb|Gmail Threading]]
Gmail's threading stacks conversation messages with the newest unread message on top and the last two emails of a thread, prioritizing usability over precise message hierarchy and '''intentionally''' allowing users to expand the rest of the messages.
 
Gmail groups emails if each message meets the following criteria:
 
* The same recipients, senders, or subjects as previous emails.
* A reference header with the identical IDs as an earlier message.
* Sent within one week of an earlier message.
 
Gmail will break an email thread if the subject line changes or the email chain grows beyond 100 emails.
 
Asking myself, is there enough context for the user? '''Context from intermediate messages can be lost''', potentially leading to misunderstandings or incomplete information. The condensed view might not provide enough information for users to decide whether to open a thread or not.
 
Also the system could automatically groups messages that are nor supposed to be grouped.