|
|
|
|
|
|
by shwinnabego
4244 days ago
|
|
|
I think your comment conflates purpose and efficiency. This might be because you've only used slack for a few days now, and haven't realized its full power. While email can be used for group communication, it's not ideal for the typical, constant interactions of a small team. Let's consider one use case. In email, file sharing with an individual is a multi-step process (new message, select recipient, insert subject, add attachment, write comments, send). In slack, you click upload, select file, and it's sent. No formality or friction in creating a new thread, selecting recipients, ad infinitum. Not to mention, it's hard to discover all the files shared between you and a group of people via email. This is important in an organization. A similar argument could be made for search and group messaging. This snap judgement is the equivalent of suggesting that you'd forgo wearing gloves in the winter because wrapping warm pieces of fabric around your hands serves the same purpose. Purpose ≠ efficiency. p.s. the desktop app > keeping a tab constantly open :) |
|
|
That's not so much a feature of "using email" as "the UX of a typical general-purpose email client". But, heck, the UX of sharing-via-email from even a typical Android app is somewhat more streamlined than what you present, and the same is true of many desktop apps that have email distribution as a feature. The recieving side is still a problem, though the kind of progress in email clients we've seen with -- just to look at gmail as an example -- schema-based actions and Inbox's workflow -- suggests that we may not be too far from the time when the recieve workflow for document-sharing-via-email is improved, after a fairly long period where email client workflows were fairly static.