I think it's well known at this time that the android os handles running apps and most if not all apps do not have a 'close' button
Out of curiosity though, how does the OS and the apps handle this. One of my biggest gripes with the DI is battery life. With all the applications that are running, I'm sure it has some sort of affect on the battery life.
What I'm curious about is say for an app such as AIM, when compared to say a game such as robo defense. I'm guessing the AIM app is built in such a way where the developers tell the OS what part of it needs to be "running" (receiving IM's and etc) where something like robo defense when written tells the os that it can run in the background but can be in suspended mode?
Out of curiosity though, how does the OS and the apps handle this. One of my biggest gripes with the DI is battery life. With all the applications that are running, I'm sure it has some sort of affect on the battery life.
What I'm curious about is say for an app such as AIM, when compared to say a game such as robo defense. I'm guessing the AIM app is built in such a way where the developers tell the OS what part of it needs to be "running" (receiving IM's and etc) where something like robo defense when written tells the os that it can run in the background but can be in suspended mode?
Facebook
Twitter
Instagram