August 9, 2020
Earlier this month we released Delivery Receipts! So what does that mean for you and your chat implementation?
Your users now will have complete confidence that their message has been delivered to their intended recipients. And you as the developer will now have more flexibility on what you choose to do once the message has been delivered. Whether that be as simple as displaying an icon to show the message was delivered, or as complex as handling additional events in-app upon the message being delivered. The release of Delivery Receipts is another feature that enables you as the developer to continue providing a world-class chat experience for your users with little effort on your end.
What this also means, is that with the release of Delivery Receipts, Sendbird has completed you and your user’s visibility into the entire messaging lifecycle. In this blog, we will talk a bit about the message lifecycle as it exists in Sendbird, and provide you with some background as to how it can be implemented fully into your chat.
What is the messaging lifecycle?
The messaging lifecycle simply put is the journey of a message, from the thoughts being typed into words, to the recipient reading the message themselves. Prior to Delivery Receipts, the messaging lifecycle in Sendbird from the perspective of the sender would have looked something like the following:
Sender types a message and sends it Message is sent to the server (With built in offline messaging to handle cases of poor to no connection) Message is read by the recipient
While this did cover most bases there could be a lot of uncertainty between steps 2 and 3. Until the recipient actually checked that chat and marked the message as read, the sender would have no idea if the message was successfully received by the recipient or not. The sender would be left wondering if the reason they saw no response was as a result of poor connection, or simply the recipient hadn’t gotten around to checking their chat yet. All these worries are in the past as now the life-cycle looks a little more like this:
Sender types a message and sends it Message is sent to the server (With built in offline messaging to handle cases of poor to no connection) Message is delivered to the recipient’s device Message is read by the recipient
With the introduction of that crucial step between the previous 2 and 3 the lifecycle now takes on a completed picture. Whereas before the sender would have no idea if the receiver ever got the message until the read receipts were updated, now within moments the sender can confidently see its been delivered and go about their day.
Messaging Lifecycle Notifications
Great, so now that we’ve talked about why delivery receipts are so crucial to completing the message lifecycle let’s go ahead and take a little more of a technical look at some of the features Sendbird offers and how easily they can be implemented into your app.
1. Sender types a message
The first part of the message lifecycle is fairly straightforward. At this stage, there are a few features that we should highlight which will take the message lifecycle and make it a little more clear as to how itContinue reading