![]() ![]() The chat service uses SendBird to create users, chat channels, and channel metadata, and then stores that data. In the data store we maintain users and channels that get created by SendBird. The chat service handles communications between the data store and SendBird platform APIs. Mobile clients connect to the chat service to get the chat user and chat channels. The in-app chat entry points have been added to all of DoorDash’s mobile clients. Our system design consists of four main components: mobile clients, chat service, data store, and SendBird SDKs. It also provides elegant pre-built UI components. Comparing SendBird and Pubnub, we finally decided to go with SendBird because of its easy-to-use chat API and a fully-managed chat platform on the backend. Twilio got excluded from our analysis almost immediately because it does not provide a customizable UIKit and lacks some of the features that SendBird and Pubnub provide. We evaluated each option thoroughly and decided to go with SendBird. ![]() Our survey of chat technologies resulted in a shortlist comprised of SendBird, Twilio, and Pubnub. A few secondary requirements included content moderation, high quality documentation, and the ability to integrate chatbots. VoIP adds the capability for voice chats, which can, at times, be more effective than text chat. The user interface kit lets us integrate the chat interface into our apps while preserving the DoorDash look and feel. Both the chat history and read receipts help our customer service agents review interactions and solve issues. Push notifications ensure that Dashers and customers know they’ve received a message.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |