alt Hacker NewsiOS I think has really aggressive background task killing, and it also drives me insane. I know they do it for battery life but I'm about ready to switch to Android, and would have a long time ago if I that didn't also mean replacing my watch, headphones, etc.
Is it too much to ask for me to manage my own background processes on my phone? I don't want the OS arbitrarily deciding what to pause & kill. If it actually does OOM, give me a dialog like macOS and ask me what to kill. Then again, if a phone is going OOM with 12GB of RAM there's a serious optimization problem going on with mobile apps.
Replies
iOS doesn't have aggressive background task killing except for memory pressure. It suspends apps for battery life; it only kills them under memory constraints. If you don't want apps dying and tabs closing, use apps that use less memory. iOS does not have swap out of a desire to avoid unnecessary NAND wear (and to avoid the performance impact), so it must more aggressively kill things.
I recently started learning how to do iOS apps for work and the short answer is: you don't.
Apple seemingly wants all apps to be static jpegs that never need to connect to any data local or remote, and never do any processing. If you want to do something in the background so that your user can multitask, too damn bad.
You can run in the background, for a non-deterministic amount of time. If you do that, iOS nags your user to make it stop. If you access radios, iOS nags your user to disable it.
It's honestly insane. I don't know why or how anyone develops for this platform.
Not to mention the fact that you have to spend $5k minimum just to put hello world on the screen. I can't believe that apple gets away with forcing you to buy a goddamn Mac to complile a program.
> iOS I think has really aggressive background task killing, and it also drives me insane. I know they do it for battery life but I'm about ready to switch to Android, and would have a long time ago if I that didn't also mean replacing my watch, headphones, etc.
Android does all sorts of wacky stuff with background tasks too... Although I don't feel like my 6 GB Android is low memory, so maybe there's something there, but I also don't run a lot of apps, and I regularly close Firefox tabs. Android apps do mostly seem well prepared for background shenanigans, cause they happen all the time. There's the AOSP/Google Play background app controls, but also most of the OEMs do some stuff, and sometimes it's very hard to get stuff you want to run in the background to stay running.
I dunno about watches, but Airpods work fine with Android, as long as you disconnect them from FindMy cause there's no way to make them not think they're lost (he says authoritatively, hoping to be corrected).