4 ms·
That's a pretty horrifying story about those push notifications. The biggest use case of my customers for creating native apps around web apps for iOS is push n
by dep_b 8y ago
That's a pretty horrifying story about those push notifications. The biggest use case of my customers for creating native apps around web apps for iOS is push notifications, that's immensely huge for businesses. Losing push notifications means your application loses it's value.
- sgc 8y agoAlthough probably not push itself as a mechanism, this interfering trend is so bad that for a time I could not find a timer or alarm that would actually ring at the right time. I have one now, but there should have been zero instances of failure to notify for a timer.
- Arnt 8y agoOn the other hand, there should also be zero instances of battery-burning apps, and zero instances of unkillable apps. IMO the blame belongs mostly to the thingies that kills apps so hard that Android blacklists them, and won't start them again until the user explicitly does it. That Android has that blacklist is understandable; that "battery savers" get innocent apps added is IMNSHO offensively shoddy.
- sgc 8y agoI had no idea they did that. Does Greenify work that way?
- Arnt 8y agoNever tried Greenify. But the two I've seen close apps in a forcible manner that Android cannot distinguish from a buggy app that crashes repeatedly when restarted. Then Android revokes the app's right to (re)start itself. The user retains that right. But the app cannot e.g. schedule anything to be run next time the phone is on WLAN, or next time the battery is being charged.
- fyfy18 8y agoWhy does push notifications on Android require the app to be running? On iOS, as I understand, you tell Apple to send a notification, which is received by a service on the device, which triggers your app to do a little processing and show the notification - why is Android any different?