Mac.newby wrote:
ok wrong word. They were never started - and then suspended. They are available for dispatch by IOS - right?
Yes. That is a list of apps that have been used; it is only a list. It is not apps. Here is the long answer:
I’m going to try to dig into what the App Switcher is. This is based on my knowledge of operating systems in general and how virtual memory works; it probably is not 100% accurate, but should be close.
The App Switcher does not contain apps. Essentially it is just a list of apps that have been used. I’ll call them “stubs”. Each stub contains the ID of the app, and the last state the app was in when it last ran. If the app has a code segment in RAM it also contains a pointer to that code segment. But the stub is very small, probably just a few hundred bytes (if that much). When you relaunch an app either from the Home screen or the app switcher the list is consulted, and if the app is in the list either the code segment is activated so it can resume where it left off, or if it is swapped out, it is reloaded so it can resume where it left off.
If the app is not in the list the app is started from scratch; its entry code segment is loaded, and it must run its initialization code, open its resources and then go on to its working code. This takes longer than just activating it from the app switcher, and uses more energy than just activating it from the app switcher, so for this reason killing apps unnecessarily uses more energy than just leaving them in the app switcher list. Probably not a lot more, but some.
But as they are just stubs, none of the apps in the app switcher are “running”.
When you kill an app in the app switcher the next time it is needed it must be reloaded as I described. But also consider what happens when you kill an app. If you first exit to the Home screen, then kill it, you probably won’t do any damage, because exiting to the Home screen allows the app to save its state in storage and be in an idle state when you kill it.
Some people kill an app by going to the app switcher and killing it while the app is still “running”, rather than exiting to the Home screen first. This can have unpredictable results, because killing an app stops it RIGHT NOW, right in the middle of what it was doing. This can result in lost data. The most egregious example of this was when the “unsend” feature was added to the Mail app. A lot of posts complained that their mail never sent, and it was because they killed the Mail app from the App Switcher without waiting for the message, which was only in RAM, to send. Apple DID fix this, by saving the message to the Outbox as soon as Send was tapped, and before it was sent. The same thing can happen with Messages, if you exit directly from the app switcher, and it is also true for many 3rd party apps.