News for hackers. Stuff that matters.

A comment on Android vendors, don’t kill my app. Parent comment

Re:Android vendors, don’t kill my app by scarface74 on Monday January 14, 2019 @06:30AM (#18902248)
It makes Android overall seem more buggy (for example, not receiving notifications for an instant messaging app is pretty ridiculous, assuming I’ve opted in and want these notifications).

Do instant messaging apps really need to be running to listen for notifications? Why isn’t listening for notifications being handled by one central Android process that then dispatches it and launches the app if necessary?

[ Parent | on HN ]
Re:Android vendors, don’t kill my app by GeneralTspoon on Monday January 14, 2019 @06:52AM (#18902352)
That’s exactly how it works - but this service itself is throttled.

And, in Android 9, “App Buckets” will increase/decrease throttling depending on your usage of the app.

For example, an app that you don’t open regularly, but do want receive timely notifications from (like a banking app, or calendar/scheduling app), might only get 1 window a day where it receives notifications.

[ Parent | on HN ]
Re:Android vendors, don’t kill my app by scarface74 on Monday January 14, 2019 @07:06AM (#18902413)
There is a difference between a notification that is sent to the user just to tell them something and then the user can take action (meaning no need to wake up the app) and a notification to the app for the app to do something in the background.

The former should always get to the user, the latter on iOS is controlled by both the OS based on an algorithm and by the user who can specifically turn off background processing on a per app basis on iOS.

[ Parent | on HN ]