Don't depend on Firebase for Push Notifications
D
DoHn
I've moved to Stitch from Firebase because of the lack of support for React-Native and I've just discovered that I need to use Firebase to receive Push Notifications from my Stitch App. I'm aware of the complexity of adding this layer to Stitch's SDKs, but you're already much ahead of Firebase in terms of SDK maintenance and support, being able to make an app's stack Stitch-only would be wonderful for many, I think.
Drew DiPalma
Hi Folks!
As part of our upcoming re-brand of "Stitch" to "Realm" we'll also be migrating our feedback forum and joining the rest of MongoDB at feedback.mongodb.com, as part of that transition, we'll be shutting down this forum. We're still keeping track of this feedback and all of the related comments/discussions, but all future updates will be made here:
https://feedback.mongodb.com/forums/923521-realm/suggestions/40550671-broader-push-notification-support
Drew DiPalma
Merged in a post:
Push Notifications using Mongo Functions
Rashanjyot Singh Arora
Sample code for sending push notifications using mongo functions is unavailable and documentation is not complete too! Push notifications are successfully sent manually but I wish to send them when trigger executes. It always yields "InvalidRegistration"
Bennett Rasmussen
The real draw of FCM is that it does greatly reduce the difficulty of sending push notifications and it works great (when you figure it out). I think the real annoyance here is that you still need the FCM client library to get the device tokens which significantly increases the build time (especially on RN). Perhaps fork/implement what FCM did there into stitch so it's capable of grabbing device tokens and you don't need the FCM SDK but still send the token and notification payload to FCM?
James Tan
i totally agree. especially when we need to handle china market, firebase is out of the question. other optional providers are onesignal