It requires significant effort for us to build out support and triage issues on each browser, so we're focused on providing a great experience in Chrome and our desktop apps. We are listening to all feedback, though. 👂
As someone who doesn't like native apps in general ( I mainly use Linux & OpenBSD anyway so native apps for many proprietary software doesn't exist in those platforms because the companies don't care), I disagree. If you can do it in the browser, why not?
Lollerskates... they have to do what is right for their company. If Firefox is a mess to support, are you saying they absolutely must only rollout a feature if it is on all browsers? And, like they said, desktop app works just fine, so there is certainly a choice for everyone.
Should work cross browser and do work cross browser are two different things. I still can't get WebEx to work and have downloaded like 8 things. If it's too much hassle to support, companies won't do it. It's frustrating for users but such is life
I've been a paying customer since the early days of @SlackHQ. We're a diverse team spanning operating systems and browsers, relying on your wonderful service to do our work. This attitude is damaging to the web, and I urge you to reconsider.
We're afraid our first response may have come off a little more limiting that we meant it — we're focusing on Chrome for our calls support specifically, but that does not mean we have no plans to expand to other browsers in the future!
Howdy! PM on the Edge team here. We'd love to connect with your team if there is anything blocking you from lighting up calling in Edge and other browsers. Feel free to reach out to me directly (DMs are open or kypflug at microsoft). Cheers!
Wow. The idea that you'd view browsers as separate platforms you'd have to "expand" to is frightening and *very* disappointing. I thought you guys had a pretty good thing going, but this will be difficult to see past. (Especially as I'm currently moving away from Chrome.)
Wow. Slack is the last company I expected to see something like this from.
This thinking is completely backwards. Web standards are not new. Building for one browser was damaging to the web 20 years ago, and it's still damaging today.
We misspoke some, sorry folks. We don't mean to say that expanding here isn't a possibility, but at this moment we're not at a spot where we can prioritize this support. This kickstarted an internal discussion, though, so thank you. Appreciate the feedback.
The day Slack stops working in #Firefox is the day we ditch Slack. Code to #standards, not browsers. We already went through this nightmare with #Microsoft and sites that only worked w/ IE. #Microsoft got roasted for that, Slack wants the same?
"It requires significant effort for us to build out support and triage issues on each browser"
Yeah. Welcome to what everybody else has to do as part of their web development job unless they want to get fired.
This is some premium anti-web BS. If supporting @firefox is causing you that much of a headache you've done something incredibly wrong. Any pull request that doesn't work in 95% of browsers should be rejected IMO.