Stream Chat vs. Vonage Communications APIs

Based on my experience, here are some scenarios where Stream Chat is well suited: 1. If you want to build a real-time chat system then it is a very important use case. 2. Also good if you want to integrate it into gaming applications. However, there are also scenarios where Stream Chat may be less appropriate. For example: 1. stream chat use cases are mostly for real-time messaging use cases only but if you are someone who don't have such use case than you can skip stream chat

Incentivized

While there are likely a variety of scenarios that would work well with Vonage [Communications APIs (formerly Nexmo)], implementations that need transactional message and response actions are a great fit. Our experience with transactional messaging has been really good and we are continuing to look at opportunities to expand our usage of this part of their service.

• Well, if there's a need for real-time messaging need then stream chat is there for the help.
• Multi-platform support of Stream chat is really good. It supports a range of platforms like web, desktop, mobile.
• Also it is very easy for developer to customise there need with the help of its documentation which make it very easy to implement.

• I like the delivery speed, it's very instantaneous. As soon as the delivery status changes on the website, the message gets delivered. The rates are also cheap and affordable.
• The accuracy of the services and the non-stop supportive team.
• Simple API, easy to integrate with existing notification functionality in your Laravel apps.
• Ease of implementation. We needed less than one month to go live.

Incentivized

• Better documentation on more subtle use-case scenarios

Incentivized

• Written documentation and discovery could be a lot better.

The overall usability of Vonage [Communications APIs (formerly Nexmo)] system for message delivery is sufficient for our implementation. Some improvements and additional reporting options in the account administration interface would increase our utilization of the post-delivery data further in order to provide further value-added features for our clients.

The product feels a bit like a black box since it's built to be an off-the-shelf solution so sometimes it feels like the only way to really understand it is to talk to an engineer directly as the documentation is so-so.

Why we prefer stream chat over Twilio was as follows: 1. User interface customization: Stream Chat provides wide range of user interface customization feature than Twilio. 2. Moderation tools: Stream chat provides a lot of moderation tools to manage chat and content being generate real time on the app. 3. Collaboration features: collaboration feature of stream chat is really good. Very simple collaboration features are provided by Stream Chat

Incentivized

Nexmo is the best platform in the industry for sure. We don't use all the features that the API provides but we are really satisfied with the ones we use. We are sure this is the best solution in the market if you need to solve the communication in real time with your customers. When we have to build a new website we are going to support the solution with Nexmo.

Incentivized

• stream chat saved a lot of our cost which we may have invested in building our own messaging system
• stream chat saved a lot of our time which we may have invested in building our own messaging system
• overall the ROI for us with stream chat was higher

• Allowed us to go to market faster (positive).
• Greatly limits our claim to quality as the ceiling on video quality is lower than other platforms (negative).