Re:Designing an email-only Slack interface
by cryath on Wednesday July 04, 2018 @12:48PM
(#17458198)
I don't see anything wrong with the majority of asynchornous communication methods. Mind you, I'm a fan of slack and a lot of people aren't. The issue though, I think, and the reason why slack is so widely used despite the fact that most users tend not to like it is because of the UI. It's friendly and easy, for surface level tasks, and that's far more important to people than the fact that it's synchronous (based off of my own experience, can't cite any stats so I'm not making a claim here). Email could very well work for this, and several apps have tried to "IM-ify" email, but none have really caught on. It's a UI and UX issue fundamentally, not a capability issue, once again according to my experience.
Re:Designing an email-only Slack interface
by PretzelFisch on Wednesday July 04, 2018 @11:50AM
(#17457863)
I often feel that what is horrible with email is the ui.
As mentioned in the article "... that company communicated almost entirely via Slack" So where do I digg up the rest? It might be in a voicemail of a colleague.
If slack would implement a push-IMAP api. I could at least drop one app :)