But the apps themselves are closed...depends on what you want, to actually close the apps or to clear the list of recently used apps.The list of recently used apps comes back when you restart the IOS device.
But the apps themselves are closed...depends on what you want, to actually close the apps or to clear the list of recently used apps.The list of recently used apps comes back when you restart the IOS device.
Yeah, for that purpose, aside from some jailbreak tweak, the only real option you have (at least so far) is to swipe away the apps yourself whenever you want to clear them out.I want to clear the list periodically, for no good reason other than keeping things tidy #
These threads are depressing. Repeat yourself as much as you like, but there is no need to close down apps unless they're malfunctioning. None.
1- yes maxing memory isn't bad per say. But if you have 2% free instead of 50% free your device will be physically slower. I'm a computer engineer and can say that with certainty from both logic and experience.
You're flat wrong, mr computer engineer. Read up on how this actually works in IOS as opposed to how you think it works on a PC.
Excellent suggestion to read up on this. The paragraph below is from the iOS App Programming Guide (emphasis mine):
Because the iOS virtual memory model does not include disk swap space, apps are more limited in the amount of memory they have available for use. Using large amounts of memory can seriously degrade system performance and potentially cause the system to terminate your app. In addition, apps running under multitasking must share system memory with all other running apps. Therefore, make it a high priority to reduce the amount of memory used by your app.
There is a direct correlation between the amount of free memory available and the relative performance of your app. Less free memory means that the system is more likely to have trouble fulfilling future memory requests. If that happens, the system can always remove suspended apps, code pages, or other nonvolatile resources from memory. However, removing those apps and resources from memory may be only a temporary fix, especially if they are needed again a short time later. Instead, minimize your memory use in the first place, and clean up the memory you do use in a timely manner.
I simply prefer to not have my system dispatch low-memory warnings and rely on the apps to clean themselves up in the allotted five seconds, only to possibly bounce back into a low-memory condition (rinse, lather, repeat).
If you don't remove apps from your recently used app list and don't have problems, great! But resetting an iPhone to launch Real Racer or X-plane, or Settings opening slowly on my kid's iPod that has many items in the recently used app list is an indication that Apple is correct when they say that the amount of free memory has an impact on system performance.
I simply prefer to not have my system dispatch low-memory warnings and rely on the apps to clean themselves up in the allotted five seconds, only to possibly bounce back into a low-memory condition (rinse, lather, repeat).
The list of recently used apps comes back when you restart the IOS device.
----------
... All it would take is a few lines of code. ...
What?That's like saying the apps come back when you re-open and close the app.
My solution still stands![]()
What?
And restarting doesn't clear out the list of recently used apps, which seems to be (at least the main part of) what the OP wants to be able to do quickly.
Spoken like a marketing exec. Too often I have heard that very comment bandied about, usually by someone who last wrote a single line of BASIC multiple decades prior too get his Commodore to do something "cool", only to have said project run months and dollars over budget simply because VERY few things in software only take a "few lines of code."
No one coding for even 5 years would ever make a statement like that when it comes to complex software designed by a team, especially an OS. Certainly not as far as making sure it doesn't affect anything and doesn't negatively affect the user. There's more than just plain coding that goes on when it comes to anything like that.i have been coding for over 15 years. i could have it done in under 30 min.
No one coding for even 5 years would ever make a statement like that when it comes to complex software designed by a team, especially an OS. Certainly not as far as making sure it doesn't affect anything and doesn't negatively affect the user. There's more than just plain coding that goes on when it comes to anything like that.
However all that is moot as Apple doesn't think that functionality is needed and in fact specifically doesn't want to provide that to users.
You do know you're reading developer notes, not instructions to the user? The point is, the system, and the apps designed for it, are designed to manage, request and release memory themselves - they do not require the user to do this for them. The situation the previous poster described where the system would slow down when only 2% memory is free - does not happen in IOS, since if IOS needs more memory it releases it, simple as that.
i have been coding for over 15 years. i could have it done in under 30 min.
Numerous threads about this but because there is really no reason to close apps in iOS. So the current method is sufficient for the times that you actually might need to. And you can close like 3 at a time if need be.