For the longer time, Android users criticized IOS for the way they aggressively killed the applications that run in the background. The multitasking capabilities of Android phones, larger memory groups and larger batteries were stirred as examples of the superiority of the platform. Of course, there are consequences for such characteristics and even Android itself has mechanisms to prevent background applications from executing. However, some manufacturers have committed it to enforce the strictest measures that can even go against Google’s policies and Android Maker now want to know who these OEM are.
Most Android applications probably do not need to always be running in the background, but there are definitely kinds of applications that make it. In fact, there is a kind of applications that should not be functioning in the background, particularly those with intentions less than innocent as malware. However, some health-centered applications may always need to run at all times, but the system may not always let these applications be.
The background applications do not come without costs, of course, generally at CPU time and, ultimately, in the battery life. That is why the platforms, including Android, establish rules and limits to which applications can do so and when. Android also makes space for exceptions and provides facilities to support sleeping applications and wake them up again.
Google also has rules for OEMs to be transparent about applications. Kill in the background and this is where things get dirty a little. Some OEM go further and beyond and implement their own application murder policies at the top of the Android and, often, do not allow developers, much less users, know who. To simply put it, some applications, such as sleep monitoring or activity tracking applications, which work on a phone, may not work properly in another brand just because the latter aggressively kills the applications that are executed in the background.
Application developers have complained about this situation for years, but it seems that Google has finally listened to his supplications. It probably helped someone to report that certain brands kill even at the important service of access to Android. Now Google is examining the developers of applications to ask about their experiences regarding this behavior.
Taking into account that this situation has been happening for years, this survey is really a time that comes. Better late than ever, as they say. Google does not even have to ask the developers personally, since the application does not kill my application, it has also existed for years, but it is likely to be better to accumulate as many anecdotes as possible for the evidence.
