> While email can be used for group communication, it's not ideal for the typical and 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).
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.
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.