1. 37
  1.  

  2. 17

    I worked on power and memory performance on the Android system layer, and I’ve gotta say, it’s frustrating how often Gruber misstates the way Android works. Android actually does a very similar thing; apps in the background are paused and their state is maintained, but they lose the ability to use the processor (unless they start a background service; I’m not sure what the iOS equivalent of that would be). Paused apps are only shut down if the phone is low on resources: in a low-RAM situation, logic that’s pretty similar to the oomkiller on linux kicks in (it decides who to kill based on a combination of LRU and RAM usage).

    I certainly will allow that iOS phones start apps a lot faster; Android is hobbled by the fact it’s starting up a bytecode JIT when the app launches. I also can’t speak for the Galaxy S8 specifically; Samsung’s done so many things to the base OS that in some ways they aren’t really running Android. In general, though, Android phones should be better at resuming than starting apps as well.

    1. 10

      The only case where I DO force quit apps is applications like Google Maps and the like which will continue to leave location services running even when the app is backgrounded - that’s some sincere battery drain there as far as I can tell. I’d be happy to have that dis-proven though.

      1. 1

        I always switch location services off when I’m not actively using them anyway. I don’t know about iOS, but Android makes this easy to do from the swipe-down quick settings panel above my notifications.

        1. 1

          There is a big blue bar at the top that says “Google Maps is Using Your Location” when navigation is on. Stop navigation -> the blue bar is gone.

          1. 4

            That’s not how it works, at least prior to iOS 11. @feoh is correct that there will be background use and battery drain. An app can use location services (and other things like downloading files) in the background. You’ll only see the blue bar if the location permissions are set to “While using”. If they’re set to “Always”, you won’t see anything.

            1. 2

              Yeah, the specific problem in question is that I see the little location services compass needle stay present long after I’ve backgrounded the app, and even when navigation isn’t running, so I generally just force quit Google Apps when I’m done with it, but that’s the only one - most apps are indeed quite happy to mellow in the background.

        2. 10

          I can think of one good reason: the background app screen/tiles/whatever gets unusably cluttered if you leave everything “open”.

          And I can think of one good UX WTF: if there’s no reason to do it, why does the option exist? Users will do everything you enable them to, so if you put a big footgun in the interface (and IIRC, the interface to close background apps on iOS is assigned to literally the only hardware button on the device), it’s on you when users shoot themselves in the foot.

          1. 16

            And I can think of one good UX WTF: if there’s no reason to do it, why does the option exist?

            There’s still a good amount of cases where the user can detect errors the operating system can’t, such as the app being logically stuck.

            1. 6

              So then in some cases you should force quit apps on iOS. ;)

              As with many things, the option probably should exist; however, in this case, the footgun is large and only a button-press away. (I’ve had poorly-interpreted swipes in the background app screen/tiles/whatever close things I didn’t intend to close.) Keep your footguns small and preferably locked up in a cabinet where they can be accessed if needed and not before, and you’ll minimize the number of traumatic foot injuries users of your interface end up with.

              1. 3

                To your first point (or maybe I’m misinterpreting it! Emoticons are tricky.)

                As Fraser mentions, yes, there are exceptional situations where an app with background privileges can get stuck, and you need to kill that app. The argument here is not that you should never have to kill any app using the multitasking switcher — the argument is that you don’t need to do it on a regular basis, and you’re not making anything “better” by clearing the list. Shame on the “geniuses” who are peddling this advice.

          2. 4

            People will still do it even if they know it doesn’t help. There’s just something nice about swiping apps you aren’t using away.

            1. 8

              Wow. Some people sure care a lot about how other people use their phones.

              FWIW, every time I use the app switch screen I force quit everything I’m not using because (IMO) it’s stupid to have a dozen things open if I’m not using them. It’s the same reason I close tabs in my browser and close apps I’m not using on my computers.

              To say it uses more battery power is irrelevant, IMO. In three or four days when I need this app again it’s going to cost a minute or two of battery life? Who cares? I have a hard time believing it’s even that much of a difference.

              The cynical part of me thinks it’s just a way for Apple to push people towards more expensive phones with more memory and storage. Or possibly it allows things like Facebook to keep tracking people when they’re not using the app. But that’s probably just being paranoid.

              All that said, though, I still don’t care what other people do on their phones.

              1. 9

                I think what’s important to note, however, is that the apps are not necessarily “open” even if they appear in the background task switcher. Apps like Facebook need explicit permission to do any real tracking in the background, and you (the user) can deny them that permission. Also, certain apps with certain background permissions may still receive notifications (say, geofence info) even if the app is not currently running.

                The TL;DR: the idea of “running” means something different on iOS.

              2. 2

                I Force Quit apps because they are bad, not for vague reasons like this.

                If I let Audible run with a sleep timer, the next time I use it the audio stutters until I FQ.

                Sometimes the Facebook app stops being able to access the Internet until a FQ.

                Sometimes Twitter forgets to give me a back button to go back to the main feed (thankfully haven’t seen this one recently)

                1. 1

                  Yeah, I use it as a troubleshooting step or to ensure Internet access is disabled. Certain apps, like Amazon or FB will almost always get a force close from me because I also use them infrequently.

                2. 2

                  Reminds me of this post about demystifying device charge times. It turns out its okay to overcharge your mobile devices and in fact it may be even better for your battery life to overcharge it some.

                  1. 4

                    Sometimes battery charging feels like nutrition science: every week an expert tells you a bit of (seemingly) contradicting information.

                    1. 2

                      The problem there is feedback: my nutrition advisor said “try out a couple of things, you’ll notice changes within a few days “ (and gave me a couple of things to try), my battery longevity has a very different and more costly feedback loop.

                  2. 2

                    So why don’t they let you swipe to clear out the apps but not close them and let you force touch the apps to force close them?

                    1. 3

                      That’s more UI and Apple is all about less UI.

                      1. 3

                        Not all devices have force touch and the interface predates force touch.

                      2. 1

                        If I can’t kill -9 ‘your app’, then I don’t want ‘your app’ on my phone.

                        1. 1

                          I remember going to an AT&T store in the states to buy a prepaid card a few weeks ago. We put the card in my iPhone and there was some initial problems with the network. So the sales person had my phone in his hand and immediately double tapped the home button and closed all my apps. I nearly jumped in his face.

                          Next time I’ll have a print-out of this article with me. If even store employees think this is a good idea, the rumor is pretty wide-spread.

                          1. 0

                            I constantly tell my wife how useless it is to force quit apps in an attempt to save battery life. Of course, she claims that it helps and that I really don’t know what I am talking about. Hey, if she believes it I guess it must be true.