restaurantnero.blogg.se - Slack vs discord

It's simply a pleasure to use Discord.Īnother thing that surprised me is that Discord seems to grow fast. I ultimately didn't expect this (I was not aware that Slack was so clunky). Using Slack in comparison to Discord feels like being in a slow mode for me now. It runs genuinely, noticeably, SMOOTHER and FASTER than Slack. What surprised me from the first second I launched the Discord app was the smoothness and responsiveness. Threaded messages - we were aware that it's missing in Discord, and in fact, it's painful.However, thanks to webhooks combined with Zapier, we could configure all integrations we had before also Discord.

Slack has a huge advantage in this space. Integrations - we were aware that Discord lacks some of the integrations we used on Slack as a mainly gamers' tool.What was expected to be worse, is in fact, worse. Also, what I like is you do not have to call somebody directly or prepare a group calls - you can enter a voice channel (Teamspeak and Ventrilo nostalgic memories.). The audio quality is excellent, screen sharing works flawlessly, the latency between you speaking and your listeners hearing it is much lower than on Slack and other solutions. The price won't change with our growing number of community users. We spend less than 80$ per month now for even better audio quality and H.D.

Pricing model - we no longer have to pay per user to keep our chat history.

In practice, all promises Discord gave us, in real day-to-day usage, turned out to be true: What's the result? What was expected to be better is better We decided to ignore the "it's a tool for gamers only' stereotype and took a bold move to try it in our organization. No history limit focus on excellent voice communication. "On paper" it looked like it could fix all the problems we had with Slack. Solution?ĭiscord? It's a tool for online gamers. It's not only a Slack issue - we tried many other tools, too, and they all often face similar problems. Sound, connection issues, and noticeable sound delay despite decent internet connection made the experience not perfect. Slack was not doing its job well in this regard. We think it's essential to communicate effectively using our tools, especially when that's the only verbal communication channel. Don't get me wrong - we are willing to pay for the tools we use, but the Slack pricing model is not well suited for a community communication tool. In this regard, it doesn't support our needs. If you want to preserve the chat history for a growing number of community users, this can get pretty expensive quickly.

What we didn't like was primarily the message history limit. This makes it crucial for us to have a tool that allows communicate flawlessly with our community and internally within our startup, as all our communication happens online. This is why we work with many different kinds of applications and need to answer various community questions. We work with all types of programmers - passionate hobbyists, innovative startup guys, serious enterprise architects, and programming newbies. We help them in deploying their applications on the cloud. Our product is focused on solving the developers' problems. Meetings, plannings, brainstorming sessions, talks with founders, technical discussions, and all the rest - it all happens online without exception. We are all distributed and work remotely. I was hired as the first full-time employee. Qovery is a remote-first startup founded at the end of the last year.