4 ms·
It's not about the protocols, it's about having a client with a user experience that is acceptable to an entire company rather than just a team of engineers. Wh
by sanderjd 8y ago
It's not about the protocols, it's about having a client with a user experience that is acceptable to an entire company rather than just a team of engineers. Which decentralized protocol has such a client? (Speaking as someone who got burned trying to advocate for IRC at a company that eventually and inevitably switched to Slack.)
- tapoxi 8y agoThere's plenty of decent XMPP clients, like Spark (https://igniterealtime.org/projects/spark/ https://igniterealtime.org/projects/spark/) but they'd take an IT team to configure. Matrix has Riot (https://riot.im/app https://riot.im/app) but personally I find it incredibly confusing.
- sanderjd 8y agoI'll have to take a look at Spark. I don't think it's a problem if something needs to be initially deployed and configured by an IT department (or otherwise tech savvy individual or group), as long as its onboarding and primary usage flows are straightforward. An arbitrary non-tech-savvy but internet-familiar employee needs to be able to create an account, browse and join rooms, and search through history without any hand-holding. Slack and its direct competitors pass this test. IRC doesn't. Does Spark?
- tapoxi 8y agoIt's certainly the closest of all XMPP clients I've used, since it has a very friendly interface. Their related Openfire XMPP server is also targeted at internal deployments and is very easy to configure with a web UI.
- ummonk 8y agoCurious why you got burned with IRC client UX given the multitude of clients available for it.
- swozey 8y agoTechnical people who haven't used IRC can barely figure out IRC their first time using it. Trying to sell IRC to a company would be hilarious. Bob in Accounting getting on IRC and feeling comfortable with it's UX?
- danmg 8y agoThen you've never seen the 'hilariously' bad UX they already put up with, with things like Quickbooks. mIRC is pretty straight forward compared to that.
- price 8y agoA hypothesis I like is that when it's an application you use to communicate with other people, people are a lot less tolerant of a confusing UX. The reason is that when you sit there clicking through a bunch of menus to find something in QuickBooks (or a typical atrocious enterprise app), nobody sees you; and if you screw something up there, you spend some more time fixing it and nobody sees the screwup. Frustrating maybe, as you waste time, but almost everyone has some frustrating wastes of time at work. If you're on IRC and people are talking at you and you sit there fumbling to figure out how to respond, it's like you're in a conversation and tongue-tied and everyone's looking at you. And if you screw something up, like send a message to the wrong channel... now you've done it in front of all your coworkers, in real time. Humans hate looking stupid in front of the group. And if you screw something up on IRC in front of your coworkers, and you're someone with even a little anxiety about not being tech-savvy... that's going to flare right up. Also, because now you're embarrassed, you're going to want something to blame. So you blame the tool.
- extra88 8y agoYes. Also, QuickBooks is accounting, which is supposed to be hard while "chatting" with people is supposed to be easy. QuickBooks doesn't have to suffer in comparison to better UX performing similar tasks in people's personal lives while IRC can be compared (unfavorably) to texting apps, Facebook Messenger, Twitter, AIM once upon a time, etc.