A few weeks ago we posted a question in our Playtomic dev blog and our developer network asking for chat solutions. Comments were broad, and we fin...
For further actions, you may consider blocking this person and/or reporting abuse
@angelolloqui really nice write up, thanks. Taking the time to explain some of your initial design decisions, particularly with the likes of Firebase, was insightful. It would be great to know how things progressed as it scaled further and whether you changed course on any of those design decisions.
I also had a specific question on how you chose to handle receiving new messages efficiently, when the user has the app open, given that each user can be involved in multiple threads. For example, did you create a "child_added" listener for each user-thread when the user opened the app, or only listen to the thread the user is currently viewing (perhaps combined with background notifications for non-active threads), or another approach entirely?
Hi @codi0 ! I'm glad you found it useful. Regarding your questions:
We still have the same design in place. We have done some minor improvements on the chat but nothing that affects the design decisions exposed in here. So far, the chat has grown a lot (a 10x since the post, with more than 1K messages a day), and we are now fully consuming the free tier and starting to pay. We are still not paying much but if we continue this trend we will have to make some design changes in a not so far future (not sure how yet).
I am not sure I understand your second question fully, but what we do to handle the multiple threads is:
Good to hear it's growing nicely. Hope that continues! And thanks for answering my slightly unclear question with so much detail, very helpful. :)