That would be great. However, it will never happen. Software has bugs, developers make assumptions. Kill switches are simple solutions that are easy to implement.
Also: which uses more battery: having a bunch of apps in the background, or having no apps in the background except recently used ones?
Having no apps in the background except recently used ones
This is exactly what iOS does seamlessly. The unused apps’ memory is dumped to disk and when you come back to it later it’s moved back into memory.
Going through all the apps and swiping up to close them is a habit that comes from early Android users and is completely unnecessary on iOS. It’s been that way for a long, long long time, so long that I would guess iOS 3 or 4.
That’s an overly simplified version of what it does; any app with background app callouts will be polling in the background… but only after it has been launched in certain circumstances. If something messes up in the app logic, that issue gets cached to storage and recovered to working memory when background or foreground functionality is called. There are two ways to fix this: kill the app, or reboot the phone (or respring if you’re jailbroken). If you know some background app is misbehaving but you don’t know which one, you can either kill them all one by one, or reboot. Killing them all would be the more efficient solution.
That would be great. However, it will never happen. Software has bugs, developers make assumptions. Kill switches are simple solutions that are easy to implement.
Also: which uses more battery: having a bunch of apps in the background, or having no apps in the background except recently used ones?
This is exactly what iOS does seamlessly. The unused apps’ memory is dumped to disk and when you come back to it later it’s moved back into memory.
Going through all the apps and swiping up to close them is a habit that comes from early Android users and is completely unnecessary on iOS. It’s been that way for a long, long long time, so long that I would guess iOS 3 or 4.
That’s an overly simplified version of what it does; any app with background app callouts will be polling in the background… but only after it has been launched in certain circumstances. If something messes up in the app logic, that issue gets cached to storage and recovered to working memory when background or foreground functionality is called. There are two ways to fix this: kill the app, or reboot the phone (or respring if you’re jailbroken). If you know some background app is misbehaving but you don’t know which one, you can either kill them all one by one, or reboot. Killing them all would be the more efficient solution.