ptinsley/gist:dd63f4a02e23c20fe4062722476f7e57

## gistfile1.txt
A bunch of polish issues (some not surprising for day one product, some are) here are a few I remember from poking around:
- each message takes up a ton of room, optimizing the whitespace feels like it's needed
- new messages by others in other threads takes the focus away while typing, SUPER annoying
- no clear indication of unread mentions in channels or indication of unread messages / threads in general
- Clicking on a wiki link mentioned in one channel that exists in another channel takes you out of that context over to the other channel / wiki with no "breadcrumb" to know how you got there or how to get back. Very disorienting, maybe an option to open wiki links in a child window or something?
- someone adding a gif to a thread: the gif plays but has the play icon with circle stuck on top of the gif even though it's already playing
- Loading of wiki pages that we were testing that had a VERY limited amount of content (a couple of lines max) was noticibley slow

The biggest issue I had with the product in my limited testing is the seemingly relentless focus on threaded chat. So much of chat today is non threaded (for better or worse) and allowing people to have that kind of interaction shouldn't be lost. I can see some value in threaded chat and am interested in the idea but am not convinced it's the *one* way things need to be going forward. Maybe having a threaded vs unthreaded option for a channel would be a good compromise. Where you can get an experience that is closer to hipchat, slack, etc... today. In my head the difference is "casual chat" vs engineering / project based chat where topic threads add real value.
	A bunch of polish issues (some not surprising for day one product, some are) here are a few I remember from poking around:
	- each message takes up a ton of room, optimizing the whitespace feels like it's needed
	- new messages by others in other threads takes the focus away while typing, SUPER annoying
	- no clear indication of unread mentions in channels or indication of unread messages / threads in general
	- Clicking on a wiki link mentioned in one channel that exists in another channel takes you out of that context over to the other channel / wiki with no "breadcrumb" to know how you got there or how to get back. Very disorienting, maybe an option to open wiki links in a child window or something?
	- someone adding a gif to a thread: the gif plays but has the play icon with circle stuck on top of the gif even though it's already playing
	- Loading of wiki pages that we were testing that had a VERY limited amount of content (a couple of lines max) was noticibley slow

	The biggest issue I had with the product in my limited testing is the seemingly relentless focus on threaded chat. So much of chat today is non threaded (for better or worse) and allowing people to have that kind of interaction shouldn't be lost. I can see some value in threaded chat and am interested in the idea but am not convinced it's the one way things need to be going forward. Maybe having a threaded vs unthreaded option for a channel would be a good compromise. Where you can get an experience that is closer to hipchat, slack, etc... today. In my head the difference is "casual chat" vs engineering / project based chat where topic threads add real value.