"While PubNub served us initially, scalability issues became apparent as our user base grew. Connectivity problems were affecting user experience, necessitating a change. The prior connection with Stream and positive interactions at Global Dating Insights (GDI) in London influenced our decision to switch."

“It (Stream Chat) is another tool that has spared us from having to reinvent the wheel, reinvent the architecture while providing us the granular control, the scalability, the reliability and the analytics layer that we need to really free our engineers up to focus on the differentiated user experience.”

"Based on the documentation, it answered many problems that I faced before. it was quite appealing and the main reason why we have Stream in the platform right now."

"It really just made sense to buy a commercially available product. We're not in a 'build' business. We're in the business of building marketplaces, not of building chat products."

"Stream's tools provided unparalleled flexibility, allowing us to replicate our previous customizations while also laying the groundwork for future enhancements."

"Stream's scalable architecture positions Jófogás for continued innovation, providing the flexibility needed to adapt and grow."

“Simple and elegant solutions like Stream Chat create a sense of community and togetherness during virtual events."

"We're centralizing information for students and giving them a full view of campus life. But we're also creating space for real social interaction—like actually meeting people, forming connections, and building community."

"Teamworks is the operating system for sports. We started out with messaging and calendar functionalities and expanded to forms after that, but we've moved into nutrition, social media, and performance management. Just about everybody in a professional sports organization will interact with Teamworks at some point in their day. If …

"A challenge we faced was syncing messages between all of the different devices users may have. We leveraged Firebase and were able to solve that problem. It solved the original needs, but we ran into other challenges as our audience grew. At that moment, we had two options: one, we …

"Ajaib previously had an in-house activity feed structure. However, user engagement was low, and we decided to retire the feature for that reason as well as to redistribute the amount of resources that were required to maintain it."

"We knew what we needed to do immediately, but we also knew what we were going to try to do in the future — we wanted to make sure we would have the ability to make channels, and customize UI, Interactions like sharing files, emojis, link parsing, add mentions, and …

“The Stream API just works, we appreciate the fact that we simply don’t have to worry about it. It’s simple for us to add new notifications and it scales with us. This gives us time to focus on other priorities.”

"There was a significant delay between sending a message and receiving it. With people so accustomed to instant messaging, we got a lot of comments on that."

"The high-quality documentation was really good, but being able to spin up a working version locally was super important. I could validate what this integration would actually feel like for the team."