I don't think Apple says there is any benefit to using that "feature". What you're seeing is a list of recently used apps. If you want to "clean up" your list a bit, go for it.
They don't market it. It's simply a way to jump back to apps you've used recently.
Does this also explain why there are constant reloading of apps for 1GB devices?For a bit more information, apps have up to 10 minutes to complete whatever they are doing (e.g. uploading a photo) when it is put into background. Upon completion or time-out, the app is in a "do-nothing" suspended state where it is just cached in memory just for quick resuming in the future. In other words, it can always be freed by iOS if necessary.
Apps also have up to 30 seconds to handle every single remote silent push notifications or Background App Refresh slot granted. However, iOS would aggressively manage these background tasks when the device is on battery. That is, the more CPU time and data the app accumulatively costs for handling pushes, or the worse the signal is, the more likely iOS will just silently drop the next turn until you put it on charger again.
There are also cases like VoIP and location services. This is just my guess, but why Skype or Facebook has reports of "draining battery" could be due to the VoIP background service, instead of their messaging service, which usually just pushes the message preview via APNS only without triggering background tasks.
It has to do something. You can't have a list of "parked" apps, each with their last state and a screencap of the last state, without it taking up resources.Apple's developer documentation makes it crystal clear, closing background apps that are not currently running does NOTHING.
Agreed. I do find at times that certain apps seem to lock up the system by running in the background. Things such as applications that use GPS, or even Safari at times will do this and upon opening it again will reload each website.I think it can help with resources to a small extent, but I don't believe it helps with performance and I think iOS's resource management is very good so this act of closing apps, has a negligible effect imo.
Yes, because when apps are in background, generally there is no guarantee that it would never be freed. Once the app is freed, the next time it is called is basically relaunching it from nothing. iOS neither has a disk-backed memory swap for inactive "anonymous" memory as on your Mac or PC, not it would preserve state for apps. Therefore, apps should implement state preservance (incl. auto-save) on their own based on their needs. Some apps actually are designed to recover the exact user state before it was put in to background, while most of the apps usually preserve only the most critical information.Does this also explain why there are constant reloading of apps for 1GB devices?
Apps that freeze or glitch can be force-quit so they restart. My messages app and ESPN radio need to be force-closed regularly. Messages freezes and ESPN get glitchy.
This. Safari gets quite glitchy pretty often for me. On occasion, even force quit wouldn't do the trick and the device needs to be hard reset.Apps that freeze or glitch can be force-quit so they restart. My messages app and ESPN radio need to be force-closed regularly. Messages freezes and ESPN get glitchy.