| > > I couldn't get that button to do anything in the demo
> See how the button changes the comment box (but yes, need to improve it) Oh, I see, all the way down there! I really expected some sort of modal dialog or similar, but it actually does work, you're right. > You're not alone! I liked Google Wave too :( > Maybe instead of injecting into the parent, we could show it in the info box on hovering the text? Yeah, that'd definitely work with how the UI currently behaves. There's still a discoverability issue with a mouseover though, not to mention the usual problem with touch interfaces - when you get to supporting phones & tablets. > > a thread for every single word is too fine-grained
> We've seen threads being created out of two words Oh, I'm sure you have! But was that a good thing to be doing? I feel like opening a discussion on a word or two is perfect for a document review tool, but for a conversation a sentence or even a paragraph would be the right unit. Then those thread summaries could appear inline too. If I think about the work related conversations I have, I'm literally the only person who posts a multi-paragraph essay I've composed outside slack/etc and checked/edited a few times. If other people were like me, this CQ2 approach would be great. However everybody else posts a sentence or two at a time as individual comments in a stream-of-consciousness manner, there's an immediate back-and-forth between 2-3 people in order to establish what's even really being talked about, and threads usually only appear when the main conversation has switched topics so people aren't chatting over each-other. There may be an element of "meeting people where they are" necessary with the product. :) |
Yep, that would be better
> for a conversation a sentence or even a paragraph would be the right unit
Interesting thought, will explore more, thanks!