Close all apps?

[PNutts]

What do you find it handy for? iOS does everything automatically for you, and you should be happy that your apps always have resources they need, never unnecessarily waste CPU/memory/battery and you never have to manage them manually.
The problem in proposing such feature is that it would do almost nothing, because pretty much all apps you see in "multitasking" are already closed, and you see just a screenshot of what they looked like when they were open last time.

That is a beautiful dream but it's commonly known that removing apps from the recently used apps list does release memory. The dream also relies on applications that follow the rules and release as much memory as possible when moved to the background.

Here's the documentation in the iOS App Programming Guide.

The important part is:

The app is in the background but is not executing code. The system moves apps to this state automatically and does not notify them before doing so. While suspended, an app remains in memory but does not execute any code.

When a low-memory condition occurs, the system may purge suspended apps without notice to make more space for the foreground app.

 

[C DM]

That is a beautiful dream but it's commonly known that removing apps from the recently used apps list does release memory. The dream also relies on applications that follow the rules and release as much memory as possible when moved to the background.

Here's the documentation in the iOS App Programming Guide.

The important part is:

The app is in the background but is not executing code. The system moves apps to this state automatically and does not notify them before doing so. While suspended, an app remains in memory but does not execute any code.

When a low-memory condition occurs, the system may purge suspended apps without notice to make more space for the foreground app.

On the other hand that does seem to imply that the system will take whatever space it might need when it might need it--so even if an app doesn't release memory on its own, if the system needs it at some point it will take it from it.

 

[aimee.elizabeth]

That is a beautiful dream but it's commonly known that removing apps from the recently used apps list does release memory. The dream also relies on applications that follow the rules and release as much memory as possible when moved to the background.

Here's the documentation in the iOS App Programming Guide.

The important part is:

The app is in the background but is not executing code. The system moves apps to this state automatically and does not notify them before doing so. While suspended, an app remains in memory but does not execute any code.

When a low-memory condition occurs, the system may purge suspended apps without notice to make more space for the foreground app.

Well if I'm understanding it correctly, in the end, it's still all automated and doesn't need user input at all. If your memory gets low, the suspended apps will automatically close to make more room for current apps.

 

[Megakazbek]

That is a beautiful dream but it's commonly known that removing apps from the recently used apps list does release memory.

It does, but the iOS does that automatically when it needs memory (so no matter how many apps are suspended, current app that's running will always get the memory it needs). And freeing up memory manually before it's needed, is just a waste of resources (you are unloading potentially useful data for nothing in return). Memory is there to be filled with data, not to sit in idle free state, and iOS does great job to keep maximum memory utilization.

 

[notrack]

What do you find it handy for? iOS does everything automatically for you, and you should be happy that your apps always have resources they need, never unnecessarily waste CPU/memory/battery and you never have to manage them manually.
The problem in proposing such feature is that it would do almost nothing, because pretty much all apps you see in "multitasking" are already closed, and you see just a screenshot of what they looked like when they were open last time.

I do see that a little different from a practical point of view. For example, when I send my navigation app to the background, it keeps running. Some apps may freeze, but some do not. The user can't really be sure that apps in the background don't waste energy or memory.

Imo the automatic handling doesn't work as well as it is intended to. It conflicts with multitasking as long as battery and memory is limited. I don't like it when there are apps in background/ in the recent-list because I don't know what they are doing or not doing.

 

[Megakazbek]

I don't like it when there are apps in background/ in the recent-list because I don't know what they are doing or not doing.

Actually, you DO know. Because if you're running a navigation app, then it gives you directions. If you're running a music player, you hear music. If you download file in Safari and switch to another app, you know that Safari will be downloading that file, because you told it to. If you have wifi hotspot enabled, your status bar will clearly indicate it, and so on.

iOS multitasking has its limits exactly to prevent apps doing random unknown things. All background actions that apps can do, are actions that you are aware of, so the problem that you describe never actually happens.

 

[Beeplance]

Actually, you DO know. Because if you're running a navigation app, then it gives you directions. If you're running a music player, you hear music. If you download file in Safari and switch to another app, you know that Safari will be downloading that file, because you told it to. If you have wifi hotspot enabled, your status bar will clearly indicate it, and so on.

iOS multitasking has its limits exactly to prevent apps doing random unknown things. All background actions that apps can do, are actions that you are aware of, so the problem that you describe never actually happens.

Excluding automatically fetching data and self-updating, of course. Some apps do that without you knowing, you might want to add that.

 

[jabingla2810]

... what's the problem in proposing this feature in iOS7?

By giving users the option to "Close all apps" it will make them believe it is something they need to do.

The iPhone and iPad should be used, they don't need to be managed.

By giving users the idea that they need to "Fully close" apps it negates all the work Apple have done.

These are phones and tablets, not Windows PC's, we don't want to regress 10 years, we wan't to move forward.

 

[C DM]

Excluding automatically fetching data and self-updating, of course. Some apps do that without you knowing, you might want to add that.

Yeah, to be fair, there are apps like Skype for example, which will continue running in the background and you won't necessarily see anything visible or hear anything to indicate that (unless a call or a message comes in, but the app will keep running even when nothing comes in).

 

[notrack]

Actually, you DO know. Because if you're running a navigation app, then it gives you directions. If you're running a music player, you hear music. If you download file in Safari and switch to another app, you know that Safari will be downloading that file, because you told it to. If you have wifi hotspot enabled, your status bar will clearly indicate it, and so on.

iOS multitasking has its limits exactly to prevent apps doing random unknown things. All background actions that apps can do, are actions that you are aware of, so the problem that you describe never actually happens.

I undestand that and it makes sense. But... How should I know where the limits are? What about when i have arrived at my destination and send the maps app to background? Does it still continue locating me? Mail, does it continue fetching emails? iCloud connected apps, do they sync in background?

Basically, what I'm trying to say that I prefer closing apps to be sure, the easier the better. The jiggle mode tapping the tiny x wasn't nice and I often wished for a close-all function. Swiping up is a great improvement.

 

[WordMasterRice]

I do see that a little different from a practical point of view. For example, when I send my navigation app to the background, it keeps running. Some apps may freeze, but some do not. The user can't really be sure that apps in the background don't waste energy or memory.

Imo the automatic handling doesn't work as well as it is intended to. It conflicts with multitasking as long as battery and memory is limited. I don't like it when there are apps in background/ in the recent-list because I don't know what they are doing or not doing.

Wasting used memory is an oxymoron if I've ever heard it. If an app is using memory then it isn't being wasted, if however your phone has free memory, that is being wasted. Free memory is 100% useless.

I undestand that and it makes sense. But... How should I know where the limits are? What about when i have arrived at my destination and send the maps app to background? Does it still continue locating me? Mail, does it continue fetching emails? iCloud connected apps, do they sync in background?

Basically, what I'm trying to say that I prefer closing apps to be sure, the easier the better. The jiggle mode tapping the tiny x wasn't nice and I often wished for a close-all function. Swiping up is a great improvement.

It is not possible to close mail.

 

[Sodner]

Closing apps is a "windows" mentality.

In iOS and OS X it is not necessary. It's a different way of thinking. YOU feel better having closed the app you are no longer using, but it's simply not necessary.

 

[hakr100]

The beauty of jailbreaking, at least to me, is that it allows me to set up and use a device the way *I* want to use it, as opposed to how Apple demands I should use it.

 

[dcp10]

I like to keep my task switcher clean for efficiency's sake. If I have to make multiple swipes to find the app I want I might just as well find it without using the task switcher.

I think a close all apps would be a welcome function. Maybe it could be implemented by swiping up on the home screen image in the task switcher view since it's there and apparently not being used for any other purpose?

 

[Jakimo]

Wow, I didn't notice before that you can throw out three at a time! Doesn't work in Safari tho..

 

[Armen]

I like to keep my task switcher clean for efficiency's sake. If I have to make multiple swipes to find the app I want I might just as well find it without using the task switcher.

I think a close all apps would be a welcome function. Maybe it could be implemented by swiping up on the home screen image in the task switcher view since it's there and apparently not being used for any other purpose?

swiping up on the home screen card to close all is a Brilliant idea.

 

[C DM]

Closing apps is a "windows" mentality.

In iOS and OS X it is not necessary. It's a different way of thinking. YOU feel better having closed the app you are no longer using, but it's simply not necessary.

Clearly, as mentioned in a few replies in this thread, there are cases where it can be useful if not even needed for one reason or another.

 

[Sodner]

Clearly, as mentioned in a few replies in this thread, there are cases where it can be useful if not even needed for one reason or another.

Although I do agree with you, in that getting rid of apps your done with seems like the right thing to do, all indications are it has no benefit. The OS will kill apps when it needs to. Killing them before hand, does nothing.

Like someone else said, free memory is wasted memory.

But having used windows all my life, there is a comfort that comes from closing what your no longer using.

 

[C DM]

Although I do agree with you, in that getting rid of apps your done with seems like the right thing to do, all indications are it has no benefit. The OS will kill apps when it needs to. Killing them before hand, does nothing.

Like someone else said, free memory is wasted memory.

But having used windows all my life, there is a comfort that comes from closing what your no longer using.

But again there are apps that can stay in the background and keep on using resources without the user realizing it or noticing it. There are also apps that can get into a weird state and get stuck. So there's something to be said for those. These aren't really common things perhaps, but they do happen enough where closing down those apps at least (and sometimes it might be hard to know which ones they are exactly) would be helpful actually in one way or another.

 

[Jakimo]

Although I do agree with you, in that getting rid of apps your done with seems like the right thing to do, all indications are it has no benefit. The OS will kill apps when it needs to. Killing them before hand, does nothing.

Like someone else said, free memory is wasted memory.

But having used windows all my life, there is a comfort that comes from closing what your no longer using.

That isn't true. There are some games that after an iPad or iPhone has been in use for some time, won't launch or starts to crash - unless you kill recently used apps.

I don't come across this much myself, but my kids who use their iOS devices for games find they must kill apps to get certain games enough headroom... and that by recommendation of many gamers by the way! Old news, old trick..

 

[PNutts]

On the other hand that does seem to imply that the system will take whatever space it might need when it might need it--so even if an app doesn't release memory on its own, if the system needs it at some point it will take it from it.

This is true.

Well if I'm understanding it correctly, in the end, it's still all automated and doesn't need user input at all. If your memory gets low, the suspended apps will automatically close to make more room for current apps.

Correct, but Apple doesn't speak to the performance and user experience of a "low memory condition" when it starts to purge suspended apps to reclaim memory.

It does, but the iOS does that automatically when it needs memory (so no matter how many apps are suspended, current app that's running will always get the memory it needs). And freeing up memory manually before it's needed, is just a waste of resources (you are unloading potentially useful data for nothing in return). Memory is there to be filled with data, not to sit in idle free state, and iOS does great job to keep maximum memory utilization.

I disagree that a new or current app gets the memory it needs to launch and/or run well. I'm also putting the responsibility of this on the application.

Closing apps is a "windows" mentality.

In iOS and OS X it is not necessary. It's a different way of thinking. YOU feel better having closed the app you are no longer using, but it's simply not necessary.

I agree that's how it's supposed to work and don't want to be argumentative, but it doesn't work as well as it should. I simply disagree and enjoy discussing it, but I don't expect to convert anyone.

That isn't true. There are some games that after an iPad or iPhone has been in use for some time, won't launch or starts to crash - unless you kill recently used apps.

I don't come across this much myself, but my kids who use their iOS devices for games find they must kill apps to get certain games enough headroom... and that by recommendation of many gamers by the way! Old news, old trick..

For whatever reason, some developers specifically include instructions to close recently used apps if their app doesn't launch (usually big honkin' ones like racing or flight simulators). I too pick up the kid's iPod which can have 50 or more items in the recently used apps and it's almost unusable (lengthy pauses after taps just to open settings and navigate there. Or open the app store, etc. I apps from the RUA list and the performance issues go away.

Again, its just an opinion based on observation and developer recommendations. I agree that unused memory should be utilized. But if all memory is allocated then the OS had better do a spiffy job of memory management which I don't think iOS always does for whatever reason, simply based on observation.