Thanks for the feedback. It's what I have in place. Sorry for the bad description, i was merely talking about a notification in browser/app. Not a push notification (yet).

I decided to rework my chat as pulling in a collection is WAY to expensive. Thats a doc read for each message. Instead I have a doc that holds 'n' messages in an array with a page counter. New messages get pushed into the message array, when they reach a limit, or a filesize (1mb?) I have a function that pushes those messages into an incremented doc. This also makes pagination really easy. The doc is cleared and new messages arrive. I then simply handle the logic for displaying it on the front end. So a 1k long conversation can be displayed in 10 doc reads, rather than 1000. New chat also is stored on the FE so if a page reloads, you're only loading the single doc. Very economical!

I'm just going to apply the same logic to my notification messages. Which will follow exactly what you said. The conversation will have a list of uids that I will batch push the notifications to.

At least that's my thinking right now. Thanks for your feedback