In order to truly set yourself apart from the crowd, you need to prioritize your app user’s messaging experience. An intricately and strategically built UI as discussed in the above section, goes a long way into defining that perfect Messaging Experience.
The right way to look into this is by first determining the various touch points that users have with your app’s messenger and then deciding on how to WOW the user at every such touchpoint. Now, when you decide on the WOW factors, you might want to confine yourself to the real-time and non-intrusive nature of IP-Messaging, because these are the two major factors behind its’ whooping success.
From our experience, we have seen that a typical user interacts with your in-app messenger at four distinct touch points:
I will now put light on each one of these scenarios and list out a few To-Dos for you to consider when building your application.
Users want a lightning fast experience while sending messages. Ideally they would want the message to be delivered to the receiver’s device the moment they send it. But network connectivity is not the same everywhere, so the delivery speed might as well vary. Good practices associated with sending messages are:
Last Seen At
Broadly speaking, receiving messages encompasses two scenarios:
In this section we will focus on the Foreground case, i.e. when the user is interacting with the application. The background case will be covered in the subsequent section, which is for Push Notifications & Badging.
Messaging is real-time and it can at times be the devil in disguise. Wondering how? Well when your users have to wait to receive a message and then this wait drags for long, it can easily agitate them. So it is important to set the expectations right. A few good must haves for setting this expectation right among receivers are:
Status of User
Last Seen At
Notifications play a vital role in the overall messaging experience. Purpose is basically to inform users about unseen messages when the app is in the background. It plays a vital role in re-engaging the user with your application. Hence done right, this increases retention and consequently the LTV of the average user. The best practices associated with notifications are:
Our Push Notification Troubleshooting Guide can help you, in case you are facing problems with configuring notifications.
Inability to send a message due to poor data connectivity is the most annoying part of your user’s messaging experience. This can lead to major dissatisfaction if the information being conveyed is critical and time sensitive. While there is not much you can do in this case, a good approach is to have a fallback mechanism on other modes which is not reliant on data like SMS. An advisable workaround for such offline scenarios is:
This brings us to the end of this guide. We have made efforts to cover all the possible scenarios that seemed evident and have listed down the best practices associated with each such scenario. In case we missed out on any and you would like to know our views about it, Get in Touch with our solution specialist.