I haven't followed the scene closely, but isn't it the same behavior as Apple? Can you even do background tasks in iOS?
Android vendors, don’t kill my app
11–20 of 414 posts
Re: Android vendors, don’t kill my app
#12The site lacks proper technical explanation of what the problem is exactly.
Re: Android vendors, don’t kill my app
#13I haven't followed the scene closely, but isn't it the same behavior as Apple? Can you even do background tasks in iOS?
But they have an arguably better push notification system which seems to use less battery and work better with sleeping apps.
Re: Android vendors, don’t kill my app
#14tl;dr The author would like to run his app in the background without notifying the user about it, because otherwise the author would just add add an ongoing notification, which would allow the app to run in the background forever on all platforms.
Re: Android vendors, don’t kill my app
#15I haven't followed the scene closely, but isn't it the same behavior as Apple? Can you even do background tasks in iOS?
In Android, you're technically allowed to run whenever you feel like it, but starting with Android 6, Google started limits, but I don't think apps get much feedback about when they might run, or if they can access the network when they do run. And the multitude of OEMs that are all dieing to make their product stick out means it's really a crapshoot; some oems were trying to do this before Google's release of the feature, some enable Google's version, but very aggressively, etc.
I understand the intent of these features, but there really needs to be a better way. Some apps do real, useful, work in the background, and it's not great for users when that can't happen. Many apps should probably only run when they're in the foreground. Either way, the app should be informed, so it can do the best it can, including informing users why it's not working and being able to direct users to where they can fix it, if desired.
Re: Android vendors, don’t kill my app
#16I haven't followed the scene closely, but isn't it the same behavior as Apple? Can you even do background tasks in iOS?
It seems like in Android the developer just assumes their app will be able to run in the background, except some versions just decides to kill it based on their own agendas.
Re: Android vendors, don’t kill my app
#17I haven't followed the scene closely, but isn't it the same behavior as Apple? Can you even do background tasks in iOS?
Re: Android vendors, don’t kill my app
#18I've been out of Android app development for some time, but I hang out with a few Android developers, they usually have most of the issues with Samsung, they say that there are often some quirks that have to overcome. That mostly corresponds to my outdated experience.
Re: Android vendors, don’t kill my app
#19I actually like the move to kill background tasks. Don't get me wrong I think they're great when they're needed. But if I only installed the app because the mobile site is crippled I don't want it to destroy my battery polling for content changes when I only open the app once in a blue moon.
Killing background tasks is great and Android does that automatically to save battery usage. But these manufacturers have implemented their own functionality on top of Android which cripples even critical messaging applications like WhatsApp, Slack, Gmail by not delivering Instant Messages notifications instantly.
Re: Android vendors, don’t kill my app
#20I actually like the move to kill background tasks. Don't get me wrong I think they're great when they're needed. But if I only installed the app because the mobile site is crippled I don't want it to destroy my battery polling for content changes when I only open the app once in a blue moon.
Killing background tasks is great and Android does that automatically to save battery usage. But these manufacturers have implemented their own functionality on top of Android which cripples even critical messaging applications like WhatsApp, Slack, Gmail by not delivering Instant Messages notifications instantly.