|Hacker News, Reddit, Stack Overflow Stats|
|Description||Slack brings all your communication together in one place||Supercharge team collaboration with group chat and IM||Messaging for people who make software. Integrated with your team, projects and your code.|
|Why people like using this service||
|Companies using this service|
Great product, great company
April 14, 2014 12:51
Slack filled a very complicated role and did it elegantly.
Its very well designed and easy to use. Adding integrations can be complicated but their documentation with images makes it very easy.
Also I contacted support and get a relevant answer quickly!
All this on the free plan, you better bet we will be upgrading soon.
Simple to use but user accounts could be handled better.
November 14, 2014 18:14
Slack is gorgeous and runs on multiple platforms - that's benefit #1. You can easily talk on your iMac then switch to your Android device on the fly.
The one thing I don't really like about it is how it handles multiple organization accounts.
I am a software consultant so I typically work with multiple teams over the months and it's odd to 'log into the right account'. It's not intuitive at all.
I would like there to be a way for users to easily pick a 'Persona' and not accidentally post to the wrong company.
Very useful in my daily work
February 10, 2014 20:30
I really like HipChat, not only because it's available on whatever "machine/device" you use but it has a ton of add-ons that you can integrate in you chat room that keep you and your team constantly aware of what's happening with your business.
6 Reasons To Love HipChat
April 18, 2014 12:29
Here are the main issues hard to solve with Skype but easily handled with HipChat.
Pickle #1. Group chatting Pickle #2. Offline mode Pickle #3. Sending pictures Pickle #4. Code snippets Pickle #5. Link search
And of course integrations.
We've gathered all our thoughts in an article - http://weavora.com/blog/2014/02/04/why-we-love-hipchat/
Slack is our go-to communication tool and it's slowly replacing emails across all departments of the company. We built our own Slack Bot to help us with simple DevOps stuff; Honeybadger notifies us in real time of errors happening on production in our monitoring channel; CircleCI reports builds status and deployment info as well.
→ Sud Web
We use Slack for day to day exchanges, confcalls and notification center from external services.
Slack is our primary communication tool both within a single team and company as a whole.
Get notified of build status, deployment status, github changes and internal communication for the team.
Stay in touch and record comments, chat about progress and record information that comes to light in the development and support of your project.
Algorithm practice and prepare for interview and follow software project discussion.
A vital communication tool used primary coordinate with my PM. Just a important office communication tool in general.
Group Chat, Error notifications from API, Build Process Notifications and Continous Integration Notifications. Jira Notifications about task changes.
Team coordination, and centralized reporting of deployments, code commits, code review comments, and exceptions in our live stack.
Slack is our internal communication tool of choice. We also use Slack to provide support to customers and integrate some administrative tools.
As a remote company we rely on Slack for most of our communication. Ease of sharing links, creating private conversations, and developing bots makes it a solid communication tool.
For team members not based in the head office and for working with external contractors Slack provides a great tool to communicate, stay in touch and share ideas.
I have used Slack to communicate with other developers during and after conferences and to replace email notifications from some of the sites I work on at KHM Travel Group.
Almost all company communication happens in slack, it's the beating heart of OnlineCity.
Slack is a lifesaver, not only for our day to day team communications and it's direct links into our other tools, but for Beta testing as well, with our custom Slack bot in our beta group being an invaluable asset to avoid giving our testers direct JIRA access.
Internally and with our clients, we communicate mostly through slack. We're a remote team, so Slack is our communication backbone
Our team is partly distributed, but we would still use Slack even if it weren't. Keeping conversations asynchronous ensures nobody will be kicked out of "flow" during their most productive hours.
All build, CI, and github notifications go to our dev channel. This also is where we discuss and share documents.
I first heard about Slack from my friend Matt (shout out to Final!). He was helping me out with some Rails issues so we started using Slack and I liked it. Specifically, the chat interaction. But also all the integrations. I wasn’t thinking of it as a tool to end all tools at first, just a chat tool with some cool integrations. Then I created a Slack account for StackShare, and that’s when things got real.
Sentry got easier to stay on top of, Heroku was easier to see activity from, discussions were more fluid, and the mobile app was killer. Most of the tools I use either don’t have a mobile app or have shitty ones. Slack is like a replacement for all the mobile apps my tools should have.
I don’t find Slack particularly useful for focused discussions, so I doubt it will replace email anytime soon for us. Things like product discussions/debates are best via email. It forces you to think before you type and have a clear back and forth with someone.
Small gripe: I wish Slack would disable email notifications by default, I still haven’t figured out how to turn those off.
We switched from Slack to Hipchat and have been very happy - we no longer have issues when connecting and disconnecting from our VPN, and robust editing of previous messages is a useful feature.
Internal communication and providing development updates (Bitbucket > Hipchat integration).
Hipchat provides a comprehensive and searchable chat system for development and customer relations. It is integrated with GitHub and JIRA so our developers can have specific rooms for each project, and we also have rooms for each customer tied into their Twitter feeds so we know what is relevant and can track issues via Nagios alerts.
Comunication between coworkers and get notify the other services, like to Jira; Github; Airbrake...
HipChat is fantastic for its chat and its integration with GitHub (among others). We also have our own Hubot instance named kbot, which we use all the time.
Part of our team are spread over cities and they are connected by chats or conference, sharing insights, alerts and tech discussions.
Team communications and notices, such as when a test suite has run, when commits have been made to one of our git repos.
I use HipChat to communicate with group members. I like that I can hop on and catch up on any conversations that I missed.
We debated between Slack vs HipChat, but went with HipChat because they offer free services for non profit.
Everyone in our company uses HipChat. From our help center to our engineering department, we do most of our internal conversations in hipchat rooms. Also as a remote engineering team, it is super useful to have a service like this so that conversations are logged and in the open.
We haven't found a better way to communicate directly with the core contributors and developers for many open source projects we utilize on GitHub (Scala, Scala-js, Sinatra, Apache top-level projects, just to name a few).
It is a solid piece of software that appeals to us who have used Slack in the past, and the tight integration with a single GitHub repository or organization for each Gitter room just makes sense in our eyes.