My main use case for Sendbird is to develop chats on mobile development or mobile apps and also integrate that to our backend. I developed custom chats using Sendbird-like UI with Jetpack Compose on Android and used the custom views that it brings, including their own SDK.
I used Sendbird for a chat for reporting orders. We had an app for buying things online and used Sendbird so customers could interact directly with a backend, with Sendbird portal or backend services where they could report whatever was going on with their order.
The best features Sendbird offers me is the ability to detect the state of a person, such as whether someone is online or has already replied or read the message. It is a way to be updated about how your messaging is going through status. Some applications or some SDK chats do not have enough information for getting the current status of the message that has been sent or the online activity of the end users, so that is something that is really valuable about Sendbird.
Having those status updates, such as knowing if someone is online or has read a message, helps my team and my users because sometimes if you do not see a status regarding a message, you feel you are not being talked to or reviewed. For example, if you send a message to some kind of chatbot and do not see activity feedback, such as the chat being online, the message being read, or somebody typing, that kind of thing makes the user feel more engaged. However, if you send messages and do not know whether that message was received or read, the user starts feeling as though they are not being given feedback or attention.
Sendbird is really valuable because I was able to create a chat from scratch in two to three days and a custom chat in a week by implementing things from scratch. I would say that is a really good tool or SDK to use if you are worried about speeding up and using standard behavior, because Sendbird brings almost all the features or functionality that any chat should have, such as group chat and direct chat.
For Sendbird to be improved, I would say creating more multi-platform SDKs is essential. People right now are working and do not care about the programming language itself. With AI-driven development happening, I would say include more AI-driven development or include more options on different libraries and languages.
I would appreciate keeping the documentation informed and getting more sample codes because I noticed that there were some samples that were not really up-to-date with the current development trends.
I have been using Sendbird since 2019, which is seven years.
I think everything is valuable and I have no other improvements to suggest.
My advice to others looking into using Sendbird is that they should try it because if you need to build a chat, Sendbird already has an option that behavior implemented, and you do not have to worry or lose time implementing from scratch.
Regarding Sendbird's AI capabilities, I think we need to consider how the information is being transported and what protocols we should implement so that AI cannot compromise the information security and integrity.
I think Sendbird's AI capabilities are really accurate. It has been predicting things as it is supposed to. It has cross-references and the answers are valuable. My overall rating for this review is ten out of ten.