76 Stream Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • "Dabble is a global sports wagering business that has products in Australia and the US at the moment. The Australian product is a traditional sportsbook that allows customers to bet on sports and racing events with fixed odds betting. The US product is more of a daily fantasy player statistics product where customers can place an entry on player projections."

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

  • "Episode is an interactive storytelling platform, and we use chat for our book club feature. Our main goal is to mirror real-life book clubs. We want to create a space for players to connect, communicate, and earn rewards for the stories they're reading together."

  • “Building out feed technology is quite a challenge. We made the mistake of trying to build it ourselves, and we were just stuck. From a feature perspective, we couldn’t build something as robust as what Stream can provide. I’m simply amazed at how certain features, such as ranking, work. Stream is also very easy to implement and their team has been responsive on Slack!”

  • "I am very familiar with everything that goes into building chat, When I started ShiftFlow, I knew right away — for a small team, building chat in-house is almost never a good call."

  • "The company and people profiles on Crunchbase are constantly changing, Our users, especially salespeople, want to know when these changes go live in the companies or markets that they’re interested in. By partnering with Stream, we were able to integrate a customizable activity feed into our paid products that boosted engagement among our sales users.”

  • "With Stream Chat incorporated into our application, our users will now be able to book appointments through forms directly available through chat, and we expect this new functionality to have a huge, positive impact on business.”

  • "We are at half a million MAU, and our user base is spread across southeast Asia. The two biggest markets for us are Indonesia and Vietnam, and our user base is primarily young working adults and hiring managers, ranging from millennials to Gen Z; chat is a very native interaction mode for them. So that's why we picked this form of interaction instead of the traditional email application structure."

  • "We realized that we, as Checkatrade, weren't doing enough to connect consumers and tradespeople, Providing in-app chat encourages both consumers and tradespeople to use just one communication method, reducing this common pain point."

  • "We've leveraged Stream to provide innovative audience engagement via chat, with custom reactions, verified status indicators, and user metadata to create immersive experiences. We wrapped all the features of Stream into a simple module that can be dropped onto a page to add robust chat functionality to any experience in seconds."

  • "We were looking for a write-based fan-out type of social graph because the messaging aspect user-to-users, artist-to-users was an important part of our specifications. Stream provides easy to use integrations for a lot of different frameworks including ruby."

  • "Stoked on what we are doing with @tschellenbach & Stream on @bandsintown. Great product these guys are building. They helped us build something extremely complicated that would have taken too many man hours otherwise.”

  • "Bandsintown turned to Stream to support the platform’s live chat functionality. “We needed to have engagement. In the industry of live streams, chat is a must-have."

  • “As time went by and our use cases got more advanced, we started chatting with the team [at Stream] to get answers. We feel that we established a good relationship with the team, and with time, we moved between the tiers toward a personalized feed solution. For a few weeks, our team worked in a tight relationship with the Stream team to achieve our goals for the product.”

  • "Initially, I planned to implement WebSocket communication manually using Laravel on the backend and React Native on the frontend, However, after assessing the time investment required to learn, integrate, and scale such a solution, it became clear that a more efficient approach was necessary."