Mail/Threading/UserStudies: Difference between revisions
Clearer about thread view |
No edit summary |
||
Line 17: | Line 17: | ||
Work: Outlook | Work: Outlook | ||
In Outlook, I use thread view | ==== Outlook ==== | ||
In Outlook, I use thread view. I don't normally have long conversations, unless there are long threads with multiple people, that happen during often long periods of time (some weeks or even months). | |||
How do I manage long threads: The reading is sometimes a little difficult because in Outlook you don't understand start and end | How do I manage long threads: The reading is sometimes a little difficult, because in Outlook, you don't understand start and end of the reply. It's too plain. There is a divider that doesn't help. | ||
In very long threads it would be useful | In very long threads, it would maybe be useful to summarize the content. | ||
I read everything because | I read everything, because I am usually interested in the whole conversation. I know all people who send replies. But I don't think I'd like to choose the people I read the replies from. I would not choose which one I'd like to read. I read everything. | ||
==== Feedback to our UX idea ==== | |||
I showed a picture of the mockup with threading graph | |||
Feedback: It's similar to what Outlook does already, in a less structured manner and only in the web. You can expand and see the whole thread. | Feedback: It's similar to what Outlook does already, but Outlook does it in a less structured manner and only in the web. You can expand and see the whole thread. | ||
It doesn't use | It doesn't use avatars, but you can see the chronological order of the replies that sometimes '''helps'''. | ||
I am not able to tell you if I'd like your idea, I am not used to see it. Also, people don't have often an image in the avatar, so one character is hard to interpret. | |||