Hacker News new | ask | show | jobs
by Vinnl 1676 days ago
The difference being, of course, that you only need one such application running, rather than every app that needs notifications running its own service. And of course, if a stock method every does become available, it only needs an update of UnifiedPush, rather than of every app that ships its own notification service.
1 comments

Captain Obvious, thank you. There problem is, such functionality should be at OS level to connect to chosen push notifications provider if Google Play services don't suit you. Not via some app that is subject to all android restrictions on persistent apps, including occasional unloading from memory.

The OS is designed in such way requires push notifications built into its core to work properly.

> Not via some app that is subject to all android restrictions on persistent apps, including occasional unloading from memory

Apps are subject to power and resource restrictions, but the user can easily lift those restrictions manually for certain apps, like UP Distributor. If the app is implemented properly, it will work just as well as Google's push service.

> The OS is designed in such way requires push notifications built into its core to work properly.

Notifications are built into the OS. A network-based push notification service is not part of the OS. It is false to say that (a particular implementation of) network-based push notifications have to be "built into the OS' core to work properly."

Of course, but it's not, so it's cool that this project exists and probably relevant to people's interests here, which is why I shared it.