The age old question revisited in iOS 7 — Does killing iOS apps running in the background help?

ios_7_multitasking

Ever since multitasking was introduced in iOS 4, there’s been a misconception that by closing all apps in the multitasking switcher, you’ll save system resources. The truth is that only few apps run in the background, so most of the apps in the switcher do not necessarily consume system resources.

However, with iOS 7′s smarter multitasking, the type of apps that can run in the background has significantly increased, so you might be able to see a clear difference in battery life if you keep closing apps, especially ones that have permission to run in the background.

In iOS 6, these types of apps were able to run in the background:

  • Audio: Pandora, Podcasts, Instacast, etc that stream music.
  • VoIP: Apps like Skype that let you be on a voice call even after you’ve closed the app.
  • Location: Navigation apps to continue to guide you even when you’ve closed the app, geo-fencing apps like Moves, Reminders etc. that have location-tracking or location-based alerts
  • Newsstand apps like The NY Times that download new content.
  • Apps that receive continuous updates from an external accessory in the Background.

iOS 7 includes a feature called “Background App Refresh” that allows apps to refresh their content in the background, so apps wake up periodically, and download the latest content just before you are likely to open it. The company has obviously put in a lot of effort to optimise performance, as detailed in our overview of iOS 7 multitasking, but you’d still save system resources if no apps were refreshing in the background. The trade-off would be that you’ll have to wait for new content to appear after you open the app.

If you kill an app running in the background from the multitasking switcher, it can’t wake up in the background to fetch new content, thus saving up on network, CPU cycles, and of course battery.

So the right answer to the question “Does killing iOS apps help your device” is “It depends.” It depends on what type of app is it, how often it wakes up in the background, and even how often do you use the app.

Some popular iOS apps that take advantage of the new multitasking modes are:

  • Pocket, the read-it-later app that updates your queue in the background when you add a new item.
  • Twitterrific, the Twitter client that refreshes your Twitter feed in the background periodically.
  • Instapaper, which again updates your read-it-later queue from time to time.
  • Flickr, that auto-uploads your photo library to the cloud in the background.

And a lot more!

To see which of the apps on your device refresh in the background, head to Settings > General > Background App Refresh.

IMG_3552

Of course if you don’t intend on using background refreshing, you’d be better of disabling it from here, rather than closing the app from the switcher each time after you use it.

If your iOS device’s battery life is draining quickly, then it is possible that it is due to a badly written app, so you may have to kill apps one-by-one from the app switcher to find out which app may be causing the issue [How to kill an app or apps in the background].

Do you kill apps running in the background? Let me know in the comments.

Like this post? Share it!

  • HellrideR

    iOS 7 is smart enough to not drain the battery.

  • 8lias

    Background Apps refresh: ON. Rarely kill apps. Battery: 50% left by the end of the night. Just lucky I guess.

    • Jhanna

      What iOS device do you use?

      • 8lias

        5S

  • Matt

    Had no problems at all.

  • Ha Jo

    Jason, the statement that pre-iOS7 doesn’t use resources for background apps is wrong, always has been. Yes, no task switching occurs. However, the OS must know which apps are open,many such info is stored in memory. Memory otherwise avail for other apps. Backgrounded apps can also not be removed from memory entirely: Open say a doc in a word processor. Background the app. Bring it back forward. Your doc will still be open. If you kill the app, your doc won’t be open any more. All that costs memory. Yes, the OS can kill apps when it runs short of memory. And it does so smartly by closing the app Backgrounded longest ago. However this comes with a) a time penalty and b) fragmentation problems. One can especially observe b) on older devices with less memory. Take iOS 5 on an iPad 1. With several backgrounded apps, even things like Safari become very unstable. They run much better if started on a clean memory.

    I always kill backgrounded apps. No matter how many people chant in to the rumor that it’s not necessary. Apps are more stable without background stuff.

    • JD

      exactly…people sound like idiots. yes, its not using cpu, but it is using ram. because of the limited ram of apple devices, if you dont close background apps ram consumption will usually be at 99%. If you have a jailbroken phone i would suggest installing battery doctor pro. it’s a pretty good system manager and will auto-kill background apps if they arent in use after awhile.

      • harlanhaskins

        There is no need, whatsoever, to ‘free up memory’. Memory that’s 99% full is just the system working as intended.

        • JD

          How can you say there’s no need when freeing ram has an effect on performance?

          • harlanhaskins

            The placebo effect.

  • David

    I believe you should only kill apps if you do once a week not constantly