5 ms·

Imagine how much more productive they would be with threading support. https://twitter.com/SlackHQ/status/804971838271004672 https://twitter.com/SlackHQ/status

by rl3 10y ago

Imagine how much more productive they would be with threading support. https://twitter.com/SlackHQ/status/804971838271004672 https://twitter.com/SlackHQ/status/804971838271004672 As an aside, I think it's delightful someone made a Twitter handle named @slackThreadsYet for this.

neximo64 10y ago
And if the client used some kind of reliable and fault tolerant connection method so that the app open opened up and connected really quickly instead of being behind layers of websocket over socket handshaking. At the moment it takes nearly 30s-1m from open to latest chat message visible. Instead of improving the speed they've put more effort into making the loading screens dynamic and appealing, which is quite myopic. I think i've written to Slack over 2 years ago letting them know how painful it is to use slack in Africa, Australia or where latency is high (even with a fast connection). I was hoping their valuation and billions and funding would help them improve their software or even make a native mac app.
- shade23 10y ago
  They have a native(if electron can be called native) App now for mac. I agree with the latency and performance issues though. The Slack app practically freezes on changing network or if you wake you mac from sleep.
  - eschaton 10y ago
    It's not native.
- ec109685 10y ago
  They have a plans for improving usability for remote users: https://slack.engineering/making-slack-feel-like-slack-a7c4e9b6d4fb#.7f0f5accr https://slack.engineering/making-slack-feel-like-slack-a7c4e...
hackerkid 10y ago
You should check out Zulip. https://zulip.org/ https://zulip.org/
- Novex 10y ago
  Flowdock is also pretty great https://www.flowdock.com/ https://www.flowdock.com/
tmail21 10y ago
The way chat threads are currently implemented (in chat apps other than Slack) are kind of sucky. I hope Slack doesn't do the same. Basically, the UX of chat means that threads are typically inline in the chat room or channel. This means that your threads are constantly "disappearing up". A better approach (from a UX standpoint) is to make threads first-class entities and have ways to organize threads. TMail21 (https://tmail21.com https://tmail21.com) takes just such an approach. As such it is much more geared towards the asynchronous (offline) use-case than the synchronous (real-time) use case of chat apps.

by rl3 10y ago

neximo64 10y ago

And if the client used some kind of reliable and fault tolerant connection method so that the app open opened up and connected really quickly instead of being behind layers of websocket over socket handshaking. At the moment it takes nearly 30s-1m from open to latest chat message visible. Instead of improving the speed they've put more effort into making the loading screens dynamic and appealing, which is quite myopic. I think i've written to Slack over 2 years ago letting them know how painful it is to use slack in Africa, Australia or where latency is high (even with a fast connection). I was hoping their valuation and billions and funding would help them improve their software or even make a native mac app.

shade23 10y ago
They have a native(if electron can be called native) App now for mac. I agree with the latency and performance issues though. The Slack app practically freezes on changing network or if you wake you mac from sleep.
- eschaton 10y ago
  It's not native.
ec109685 10y ago
They have a plans for improving usability for remote users: https://slack.engineering/making-slack-feel-like-slack-a7c4e9b6d4fb#.7f0f5accr https://slack.engineering/making-slack-feel-like-slack-a7c4e...

hackerkid 10y ago

You should check out Zulip. https://zulip.org/ https://zulip.org/

Novex 10y ago
Flowdock is also pretty great https://www.flowdock.com/ https://www.flowdock.com/

tmail21 10y ago

The way chat threads are currently implemented (in chat apps other than Slack) are kind of sucky. I hope Slack doesn't do the same. Basically, the UX of chat means that threads are typically inline in the chat room or channel. This means that your threads are constantly "disappearing up". A better approach (from a UX standpoint) is to make threads first-class entities and have ways to organize threads. TMail21 (https://tmail21.com https://tmail21.com) takes just such an approach. As such it is much more geared towards the asynchronous (offline) use-case than the synchronous (real-time) use case of chat apps.