Is it possible to make cross-platform PUSH notifications without using FCM?

Question

Push technologies

Good day, it is necessary to implement PUSH notifications (Web push) on the site when the user has given permission for notifications (that is, not the usual notification when the user is on the site right now - this is done in a couple of lines in JS, namely the notification to which the user has given permission and this notification is accordingly displayed when the site / browser is already closed, that is, in fact, send a push notification from the site to a user who is already offline on the site / closed the browser, for example), done through FCM (Firebase Cloud Messaging) - it turned out convenient and simple , but I wondered - is it possible to implement "your own FCM" instead of FCM, which would work both with devices on Android and IOS, and in all browsers (Chrome, FF, Safari, etc.)?

Does FCM have limits on sending push notifications or is everything free?

FCM doesn't support Huawei now, nothing has changed, has it?

I found it on github https://github.com/web-push-libs/web-push-php but as I understand it, it will cover only Chrome, but for android and ios you still need to look?

I also heard that there is one distinctive feature of FCM, which (as for me) is essentially critical - FCM (as on behalf of google) has the ability to push messages even in doze mode, so it turns out that only FCM is best pushed to androids and so far nothing else, or am I wrong?

After all, it turns out that the push service as such rests on 4 pillars: the FF browser (browser push service), Google (aka Android, chrome browser and FCM), Apple (ios and safari, you need to do them separately, but again you can integrate into FCM) and Huawei (essentially phones with their own push notification service), then why write your own service at all if all paths somehow lead to these whales and nothing can be done about it (I don’t think that ios will give api or in android will have such an opportunity, respectively, as in browsers)?

That is, in other words - for example, if you write an application for android, then in this case you can do a poll \ web socket \ keepalive in it, etc. in order to make a push notification in the future, but the push notification from the site addresses (as far as I understand) primarily to the browser, i.e. to an application for which there is no control (Chrome = Google push service, Safari = IOS push service, FF = FF push service), and the problem is that there are no super simple APIs for these push services and it turns out that FCM must be used anyway for Google, then it makes sense to separately lay forces on the implementation of FF and IOS push services, if you can leave it in FCM?

That is, in fact, FCM is practically like a proxy to the services themselves and it takes over the generation of keys, in this case, another question is how to use VAPID keys, I didn’t quite understand ... And where to get endpoints for sending push notifications to the service (for example, I found https: //fcm.googleapis.com/fcm/send , but where can I get it for others)?

Most of all I'm interested in - is there any peculiarity and advantage in using FCM and is it worth it to bother and write your own, if so, in what case?

Thank you! :)

Answer 1

It makes sense to write your own if FCM for your scale is much more expensive than a custom solution.
There's a lot to worry about, so I don't see the point.

Answer 2

1. You can write your own. It's easy for a website. For applications it is necessary to look specifically.
2. Huawei has its own free push service for apps hosted in the AppGallery.