4 ms·
I found Slack's design discussion on how they decided for single-depth threads interesting. There's a balance to strike between powerful features and usability.
by AceJohnny2 6y ago
I found Slack's design discussion on how they decided for single-depth threads interesting. There's a balance to strike between powerful features and usability.
https://medium.com/slack-design/threads-in-slack-a-long-design-journey-a7c3f410ecb4 https://medium.com/slack-design/threads-in-slack-a-long-desi...
Of course, people here have self-selected for favoring threads, but Slack's attention to the silent negatives is interesting and a lesson in product design.
- fiter 6y agoIt seems that the link to part 2 is broken. Here is a working link: https://medium.com/slack-design/threads-in-slack-a-long-design-journey-1c9b1af652c9 https://medium.com/slack-design/threads-in-slack-a-long-desi... In their testing, it does not seem like they prototyped an N-nested (indented) threading model like on Reddit or HN. I am not surprised that it would be hard to understand how all the replies fit together without such nesting.
- price 6y agoIn the context of this post, an important thing to add is that threads in Zulip also have just a single level of hierarchy - it's not at all like the tree structure here on HN, or on Reddit. We've felt that single level is the right balance for having a conversation that someone else can come to an hour later and easily read and follow. The way it works in Zulip is quite different from Slack, though. Here's a description in another comment in this thread: https://news.ycombinator.com/item?id=23863588 https://news.ycombinator.com/item?id=23863588