Ever since I got my first cell phone in 9th grade, I have been absolutely terrible at remembering to charge it. So terrible, in fact, that I’ve considered making it my go-to answer to the classic “What’s your biggest weakness?” question that always gets asked on job interviews.
In all seriousness, though, a perpetually dying cell phone sucks. So I do what I can to combat the problem. And for years, the main weapon in my arsenal has been the good ole’ Force Quit Swipe.
Here’s how it’s done.
Open the “app switcher view” or “multitasking menu” by double-tapping the home button.
Swipe through your apps like it’s a game of Fruit Ninja.
Whether you’re the guy whose phone is always dying (like me) or the girl who somehow never drops below 50%, chances are you do this too (if you have an iPhone).
Sadly, as I only recently discovered, we’re all completely wasting our time. The Force Quit Swipe is a myth.
Most of us believe the apps that appear in our multitasking menu are still running in the background, draining battery and slowing down our phones in the process.
Not true, according to a former Apple technician.
“The truth is, those apps in your multitasking menu are not running in the background at all: iOS freezes them where you last left the app so that it’s ready to go if you go back.”
A closer look
For a more thorough examination of what actually occurs inside your phone, take a look at this diagram from Apple’s app programming guide. It depicts the various execution states for apps on iOS:
And here is a description of each state:
The three that we’re concerned with here are active, background, and suspended.
When using an app, it is active. It’s using CPU and memory.
Once you press the home button, that app enters the background state, where it stays for a very short period of time before transitioning to the suspended state.
So, basically, anyone aggressively force quitting every app in sight is treating suspended apps like active ones.
To add insult to injury, there’s reason to believe that force quitting apps actually decreases battery life. Here’s that same former Apple technician to explain:
“By closing the app, you take the app out of the phone’s RAM. While you think this may be what you want to do, it’s not. When you open that same app again the next time you need it, your device has to load it back into memory all over again. All of that loading and unloading puts more stress on your device than just leaving it alone. Plus, iOS closes apps automatically as it needs more memory, so you’re doing something your device is already doing for you. You are meant to be the user of your device, not the janitor.”
It’s like turning off your car and restarting it for no reason whatsoever. All you’re doing is wasting gas.
What’s with that view after double-tapping the home button, then?
As for the multitasking menu, think of that as a “Recently Used” section, as opposed to a “Currently Open” one.
Here’s a quick little experiment to prove it:
Restart your phone. When it comes back on, double-tap the home button without launching anything. APPS EVERYWHERE, despite you having just rebooted your phone completely and opened nothing.
Force quitting apps is a surprisingly crappy idea. Hopefully, we can all agree on that now.
But how were so many of us oblivious to this fact for so long? That’s the question that really gets to me.
I mean, a single Google search will ensure even the firmest believer in the Force Quit Swipe that it’s unnecessary and ineffective.
Personally, I think it comes back to the fact that, when we’re provided information that seems logical (of course closing that app running in the background will save battery!) and the source of that information is someone we trust (a friend or family member), we rarely question it.
Even in this digital age, when every answer is just a click away, we can all still fall victim to believing in a myth.
What else do we believe in just because we were told it was true?
Get the 5-minute roundup you’ll actually read in your inbox
Business and tech news in 5 minutes or less