"There was no shared picture. You couldn't always reach the right person at the right time, and messages were often missed or repeated."

“Stream is pretty much a decision we made in the past and we don’t constantly have to worry about it. I think that’s a sign of great software because it allows our team to focus on building unique solutions.”

“From posting updates to commenting and more, Stream provided us with the most flexible and scalable solution for displaying all our user’s activities. The Stream team made implementing our news feed solution a collaborative experience and ultimately the right decision for us.”

"The core integration we built during those first two weeks is still what we use today."

"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."

“Generally, the integration went well — I think it was pretty straightforward. There was a little back and forth between our team and Stream’s team, and the support has gone well."

“Communication is a big area where I think Stream has helped us by allowing us to incorporate chat and announcements."

"We aim to challenge the superficial norms of dating. We match users based on personality, leveraging the puzzle metaphor to encourage genuine connections. In addition to the virtual realm, our in-person events have been immensely successful, prompting us to explore ways to seamlessly integrate these experiences into the app."

"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."

“Very good, the support we got from the engineers at Stream was excellent, and the documentation is good. Where we did have questions or problems, we would get answers quickly and the online documentation would be updated shortly afterward to reflect the clarification. We had to implement our own abstraction …

"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."

“By the time our event happened, there was a new performance-oriented component in the [Stream] SDK that we were able to integrate within a few hours, We had no issues with chat performance during the event.”

"Previously, we didn't have a chat interface inside our app, Communication happened on WhatsApp, and we couldn't monitor the content or protect our customers' privacy."

"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.”

"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."