Also I hope HipChat will now finally get that native OS X client they've been promising for ages.
No images or file transfers, but it's pretty pain free.
- AIR doesn't play nicely with dynamically switching graphics chips (read: all MacBook Pros and iMacs). The app itself, AIR's installer, and updater, will all randomly crash due to this, with no hint at what's wrong. The only way to fix this (if you've somehow realized this is the problem) is to lock your graphics card in System Preferences.
- It will peg your graphics card, just like Flash on Mac. You can be looking at a plain chat window and hear your MacBook Pro spinning up like a jet engine, as if you're about to do something, well, more substantial.
- It crashes, and worse, it has a really bad habit of corrupting itself when crashing. To-date I've reinstall HipChat at least 10 times on my machine. The "AIR installer crashes randomly because of graphics card problem" undocumented bug makes this even more annoying.
- It's just slow.
johnnydoe is right. AIR is like client-side Java, or any other write-once-deploy-many products. It's lowest-common-denominator crap. It has all of the limitations of its target platforms, none of its strengths, and all of the laziness that comes with trying to design a one-size-fits-all UI for everyone.
But that's just my opinion.
Just start using a chatroom and invite people in. Remind a few to add it to the auto-join list. If your coworkers find a benefit in it, there doesn't need to be an official policy; the usage will just grow organically. If they don't see a benefit, why force it on them?
Push notifications. They’re confusing. All the in-person communication is pushed, however room conversation is not unless you are @mentioned.
If you would like to make an announcement to 10 people, you have to mention them one by one manually.
I wish them luck
edit: as opposed to just building it themselves, what's so hard about a chat app? maybe i underestimate the amount of iteration in the hipchat product and they're buying that product knowledge, not the tech.
(I'm not an Atlassian fan)
Care to provide any more detail? A well reasoned post might have spared you some downvotes.
JIRA - workflow crash took our team of 30 devs at the time out entirely for 2 days. Overcomplicated administrative mess especially with respect to plugins. Reindexing takes out the entire JIRA instance until complete. Permission schemes and workflow is an epic mess of cludges.
Both products: Null pointer exceptions galore, scary memory ceiling. Integration sucks - all the horrible mappings to maintain.
They feel like bloated, slow and badly designed products which is worrying considering the cost.
TBH their support are good but I shouldn't have to use it on a product suite that costs that much.
Atlassian has made two big acquisitions that I know of (Bitbucket, SourceTree), and in both cases the product was better off after the acquisition.
From what I see, Atlassian goes in and provides cash and infrastructure, leaving the teams that were responsible for the product's success to continue making great things. I don't see any indication that things will be different for HipChat.
All your other points I somewhat agree with but to their credit they all improve steadily each release.
Be mindful that the products were source individually from various places and need a lot of work to look and work together nicely.
Let me finish on some faint praise: they are by FAR the least worse of all the 'enterprise' software we use :-)
That's like saying "they're the least bad rapist".
I do agree though!
Get onto Atlassian and get them to help you (at least with your slowness and crash issues) - their support is good once you get them engaged.
I've had all the problems you describe (large instance - 100k issues, internet facing) - sometimes it's as simple as a resetting a bad VTL template. They will get to the bottom of it.
Unfortunately, due this responsibility being approximately 5% of my time, I don't have time to invest in to-and-fro with Atlassian. I expect something to work (ironically like Trac did - its predecessor).
On the positive side, we're upgrading to latest versions soon.
Someone please save me (I'm serious there!)
I haven't used their other products (other than BitBucket, which is fine, but hasn't kept up with Github), but JIRA desperately needs a UX design vision.