I am currently working with the Push API which most browsers support by now. As in my use case, there is no internet connection but an intranet, I wanted to ask if there is any self-hosted service that can handle those push notifications.

The service would have to work using Microsoft's Edge-Browser and should support IOS-, Android- and Windows-Notifications.

Currently, I myself have only found Solutions that include a a Web API and actually doubt that this is possible. Still i thought that someone might have a solution to this problem.

Thank you in advance :-).


Upon further research, i realized that this is not a possibility:

Frankly, you don't. Native push notifications require the use of the GCM servers in the internet. Most customers allow SMP / Afaria to connect to the notification servers GCM, APNS etc and open their WiFi infrastructure in a way to give the devices also access to those servers. You should be able to nail down the ports and traffic using your firewalls etc to prevent stuff from going through that is are not notifications. Two workarounds:

Use devices that do not have an internet based notification system (e.g WindowsMobile, WinCE) ;-)

Build a notification system on IP base - e.g. have your app poll your server regularly for new items. Problem: Battery life will go bad on you as the app needs to be active a lot more and consumes much more battery this way. This is the exact reason, why the notification systems exist - the OS can receive notifications much more efficient as any app running in a sandbox could.

Under the line it is a take-it or leave-it situation. A simple fact of modern mobile life that you can love or hate :-) Cheers, Dirk

No, it is not possible to send push notifications without using the Browser Cloud Managers. Remember the Browsers implement Push API , as per the W3 Push API standard . This is what made Web Push notifications possible on Desktop and Mobile browsers. At the time of subscription these API’s provide you a subscription token, and the Browser Cloud Manager (FCM for Chrome etc.) are the only one who maintain the mapping of which subscriber token maps to which client browser. Hence, you need to use the respective cloud manager for the browsers.

Each browser is different and while they implement the standard, each has its idiosyncrasies, and hence it is often advisable to use a 3rd party vendor (like PushEngage which we run) who has build support for sending notifications on top of all browsers.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.