Thanks for the tip, and I'll be sure to mention Layer as a solution if/when we tackle this problem in the future. I just checked their site and it looks very promising.
After trying to find a solution earlier this year with my product manager, we decided to just stick to what we had (which was simply manual refresh in the messaging view by the user), due to engineering time/cost.
Since messaging is not a top priority in the app, we agreed to come back to the problem in the future. However, it is absolutely something I would like to solve given the chance. However, at the end of the day, this kind of messaging solution requires the work of backend engineers which will take up development time.
After trying to find a solution earlier this year with my product manager, we decided to just stick to what we had (which was simply manual refresh in the messaging view by the user), due to engineering time/cost.
Since messaging is not a top priority in the app, we agreed to come back to the problem in the future. However, it is absolutely something I would like to solve given the chance. However, at the end of the day, this kind of messaging solution requires the work of backend engineers which will take up development time.