I Can See This Being a Problem With 4.0

[bob616]

So far what it seems like with 4.0 is that any app you close will continue to run in the background even if you don't want it to. So the way i see it is that none technical users will have multiple applications running in the background without there knowledge and before they know it there phone is being slowed down. Also I would find it annoying to have to open up the multitasking panel every time i close an app so that I can quit it.

Any opinions on this?

 

[fishkorp]

They're not running, their state is frozen so it can resume when you go back into the app. This only happens if the app is compiled for 4.0. So every app available right now will not do that. It just gets put in the fast app switching taskbar, but the apps still relaunch each time. The only ones that keep running are the ones that use any of the multitasking APIs. And even then, in most cases, the apps aren't running, but only certain things are running (e.g. just audio streaming, the rest of the app isn't doing anything). It's up to the devs that compiles for 4.0 to not be sloppy.

 

[thelatinist]

So far what it seems like with 4.0 is that any app you close will continue to run in the background even if you don't want it to.

You misunderstand. Every application will close when the home button is pushed. The OS will simply keep a record of its state at close so that it can be reopened instantly next time it's opened. Apps which actually are doing something supported by the new APIs (streaming music, etc) when they are closed will hand off those tasks to the OS, which will continue them in the background. Closed apps will take no additional RAM unless they are actually doing something useful. The multi-tasking panel is not a list of running apps, but is essentially only a recently-used-apps list.

 

[bob616]

You misunderstand. Every application will close when the home button is pushed. The OS will simply keep a record of its state at close so that it can be reopened instantly next time it's opened. Apps which actually are doing something supported by the new APIs (streaming music, etc) when they are closed will hand off those tasks to the OS, which will continue them in the background. Closed apps will take no additional RAM unless they are actually doing something useful. The multi-tasking panel is not a list of running apps, but is essentially only a recently-used-apps list.

then when you hold the icon and it gives you an option to remove the app from the list it is just removing the state of that app?

 

[tnisatard]

yeah, i made a thread on this a few days ago


you can read some responses in there, but its really everyone arguing lol

https://forums.macrumors.com/threads/893353/

 

[jabingla2810]

Did nobody else watch the keynote?

The apps are not running in the background.

We really need to sticky something explaining this, because the lack of understanding about how the "multitasking" is going to work is unbelievable.

 

[Niiro13]

then when you hold the icon and it gives you an option to remove the app from the list it is just removing the state of that app?

Yes. Note that if the application is using one of the multi-tasking APIs, then doing that will also quit whatever it's doing in the background.

 

[ajohnson253]

If you haven't watched the keynote, watch it. The whole thing, in detail.

 

[drummerlondonw3]

what you are describing is essentially the opposite of the whole point of the multi-tasking APIs

still easily made mistake and I am sure much more information will come out nearer the time