Anecdotally, anyone working in a startup with an opinion on design will know how shallow a judgment has to be to switch to a competitor. App is functional but has 2008 design? The less functional equivalent with 2017 design is better because it looks up to date
That's completely irrelevant though.
I had never before gotten in an argument about a chat app, but HipChat made me passionate about using anything else.
That said from everyday desktop use it’s not bad. It’s nowhere near as unreliable for me as other posters are commenting about.
Anyway, hipchat's faults:
Search is garbage.
Editing a message is garbage.
Joining a room/messaging a specific person on mobile is annoying.
I'm not sure about how Slack handles it, but when a person leaves our company, our Hipchat chat history completely disappears. All those decisions we made with our old Product Manager via private message? Into the ether.
Want to delete a file you uploaded? Too bad. Maybe you can do it via the web interface?
Want to delete a message? Same deal.
3 years in, and still randomly missing messages for a while until it’s somewhat synched.
Whole ongoing conversations don’t appear on other devices if I don’t manually open them.
Getting notified on my phone while I’m on my laptop.
Lack of integrations is the most sailant thing to point st, but I think at its core Hipchap is also a very meh service.
You will find pretty annoyed people if you search for "report hipchat bug".
Google for example makes it 1000x harder to give feedback and report bugs, which greatly limits the amount of quality feedback they get.
Anecdote: hangouts didn’t let us accept external users into a hangout today. Google will never know that because I have no easy way to tel them that.
In what world would one imagine that a suggestions box was in any way different from reporting a bug? "Suggestions box" is a bug report but renamed to be understood by Joan from accounting.
So you could try to get their attention to the bug of "when you paste XML into a code block, it replaces it with subtly different, broken XML, my suggestion is to stop doing that", but it's going to be sitting several pages beyond "please add a left shark emoji!!!"
You can try to get your whole office to stack the vote, but why? I only have to be one person to report a bug to Slack.
If we have to move AND pay more money anyway, then why not just go to Slack?
If I was in charge of the decision for what communication tool to use at my company, I would take a long hard look at every single alternative to Slack.
As an example, the only way to edit a message is to use a sed-style "s/foo/bar", which is absurd. Because of this, you can't edit messages other than the most recent one, and if you want to edit one instance of "foo" but not another instance of "foo" you're out of luck. That's a terrible piece of UX even if you're in the only subset of users (software devs familiar with sed-style search and replace) where it makes any sense whatsoever
As a sibling comment said, the main reason my team abandoned Hipchat for Slack was Hipchat was hopelessly buggy and unreliable at the time we tried to use it.
HipChat is a terrible name for a work-related collaboration tool, but "Slack" isn't great either....
I guess it is a new major release of HipChat (with re-architecting) and re-branding. Same lead (Steve Goldsmith).
Unless an insider tells, we won't know I guess :)
The more recent offering (Bitbucket Server) falls behind the curve as well, even when compared to their own Bitbucket Cloud service.
Not curious enough to do the kind of blackbox exploration folks at https://webrtchacks.com or other sites do :)
Stride is a brand new product (not a rebrand of Hipchat), we did not repurpose Hipchat's code. It's built from ground up on Atlassian platform - new protocol, clients, platform, etc. One exception is the video bridge technology which remains powered by the Jitsi.org open source product (which we acquired in 2015). I do look after both products (Hipchat Cloud and Stride) for Atlassian, happy to answer questions.
Would have been a shame not to use the Jitsi technology for sure, I deeply respect Emil Ivov and team.