Pushsafer

Developer is a rock star responds quickly and the notification just works. Interface on Android is a bit old school but does what it says.

We were having problems with our in-house notification app when we found Push safer. Now we just worry about our service and let all the complexity of notification to Push safer. It's easy to use, full of features, their API is friendly and their support is a message away and they deliver fast. Would recommend to others.

Nice app and nice support. It works as expected. Be aware receiving notifications is a tricky business, and you have to understand your device settings.

Does exactly what I want to provide reliable push messages from Node-Red and Home Assistant.

Works well but I like pushover more. This one charges per API call whereas pushover is one time purchase. There are also free options available like wire pusher. However, this one also does what it advertises.

The service looked promising, but from my 1-hour experience many things look unprofessional, untested or from the previous decade. Examples: - my first attempt to call their notification service was via their pip library. OK, great - let's copy their example python script, paste my API key and see if it works. First, one of their Python examples straight up didn't work - it threw an error directly contradicting the documentation. The second example, which did finish running, threw up an HTTPS warning from urllib3. And it also didn't work - as in, no notification was pushed. (Funnily enough, the issues with Python examples were pointed out in a review here from half a year ago. Instead of thoroughly testing the Python examples on fresh environments to smooth out the new user experience, the developer decides to moan about the 1-star rating instead and suggest the lack of Python knowledge on the reviewer's side. Really? Nice PR bud.). First strike. - Since some of the reviews here comment on 'great' customer support, I decided to try it before posting a review. I click the support button, which leads me to the forum (not great, I might want to create a private ticket instead of sharing issues publicly). I see then that I need to log in again and possibly create another account just to log an issue. Again, really? It's 2021, figure out your SSO. Second strike, don't make it difficult for me to help you improve your product. - Well, guess, I'll just send an e-mail to the dev, this should be simple, right? Wrong. I go back to the user panel and find an extensive row of social services I could contact them on. Twitter, Facebook, Instagram, you name it, even weibo is there. Well, there it is, the e-mail icon right at the end. But... the mail to link is lacking the author address? So I guess even that venue of contacting the dev is broken. Third strike, I guess I'll write a review on the Play Store then... All of the above made for not the best of first impressions. However, if you're willing to overlook such annoyances, the actual delivery of the notifications was swift and very customizable (multiple types of alarms, priorities, etc.). I have mixed feelings about this, because if the developer doesn't care about first impressions which lead to sale conversions, there probably are more bugs and lack of polish lurking deeper inside. So, while it seems good enough for my current toy project, I probably will be looking for another service with a more polished experience. PS To work around the library issues, I ended up calling the generated API link directly from Python requests library, without using their buggy pip module. This actually worked.