Force-closing apps or not

[anon(10621852)]

I'm just wondering if the philosophy is the same in the Android world vs iOS world when it comes to maximizing battery health. All the years on iOS I always followed the guidance of "do not force-close apps ... just let them run the background in a sleep/rest state" - the philosophy obviously being that when you launch an app from a closed state, it takes more battery power and resource compared to opening apps that are just 'sleeping' in the background.

Does the same advice apply in the Android world, or is it recommended to do a "Close All Apps" once in a while?

Thank you!

 

[mustang7757]

Only time I force close a app if there a issue, Andriod can handle the rest.

 

[anon(10621852)]

Only time I force close a app if there a issue, Andriod can handle the rest.

Great, thank you.

In Android, when you touch the multitasking button at the bottom, and you swipe apps away, is that action force-closing the app?

 

[mustang7757]

Great, thank you.

In Android, when you touch the multitasking button at the bottom, and you swipe apps away, is that action force-closing the app?

Yeah it is , your welcome!

 

[J Dubbs]

I can't stand apps running in the background I'm not using, so I close everything I'm not actively using. Maybe I'll try leaving them open to see what effect it has on battery life. I have a landline so I turn my phone off every night.

 

[HoosierDaddy]

I can't stand apps running in the background I'm not using, so I close everything I'm not actively using. Maybe I'll try leaving them open to see what effect it has on battery life. I have a landline so I turn my phone off every night.

Suspect battery life could go either way. Starting an app multiple times could use more electricity than the app sitting idle.

 

[bkdodger2]

I've never closed any app on iOS or Android unless issue... Battery also never an issue with use or health

 

[B. Diddy]

Most apps aren't technically "running" in the background -- they're paused or cached, and therefore not actively using any resources besides the RAM they're cached in. The exception would be apps that are supposed to be doing something, like playing music in the background. But of course, some apps that are poorly designed might be incorrectly using resources in the background -- the so-called "rogue" apps -- which would show up as excessive battery usage despite not actively using the app in the foreground.