3 ms·

Killing apps in the background and offloading them from memory is a godsend for a Android ecosystem. It is literally so much harder to make anything battery opt

by ex3ndr 6y ago

Killing apps in the background and offloading them from memory is a godsend for a Android ecosystem. It is literally so much harder to make anything battery optimized since you have get information about almost everything to make it right: need radio? beware that it is in active state and only then send data. Want do background processing? Wait until user will charge it's phone. Making apps battery efficient is insanely hard task and it is solvable by just offloading everything to an OS. I have built several push services for my previous projects it always sooo hard to implement right. iOS for example, uses 25+ different parameters to optimize push delivery depending on your app usage, on how you are using your phone and so on. Good luck to build this as "third party" and keep everything private.

Andrew_nenakhov 6y ago
It is a godsend only up to a point when you can't run an app in the background even if you badly need to. The computers (and Android devices are computers) should not be putting their users into straight jackets so they won't hurt themselves. Users should have an option to do what they want. The system's job is to inform that what they are doing is using battery. If a user is OK with it, the system SHOULD NOT interfere.
- ex3ndr 6y ago
  Using such information is so hard that almost impossible. I could spend a year tailoring battery performance for a messenger and still get random guy who have some exotic phone with some strange behaviour. There are really almost no need to run app in the background or at least constantly send data without a reason (mostly just tracking). UPD: When deciding how to build something i have one small trick: first ask question about who can make better decision about something? For example? Who is more capable to make decision about battery usage, about tweaking core performance, etc? It is obviously kernel or silicone itself. App will never have required information to build perfect performant app for every device. This just means that you have to build a kernel by yourself and even more: common kernel for every phone.
  - Andrew_nenakhov 6y ago
    > Using such information is so hard that almost impossible. Aren't battery stats not enough for you? If your app uses too much battery, you can stop using it. Or you prefer some other people to make this decision for you?

by ex3ndr 6y ago

Andrew_nenakhov 6y ago

It is a godsend only up to a point when you can't run an app in the background even if you badly need to. The computers (and Android devices are computers) should not be putting their users into straight jackets so they won't hurt themselves. Users should have an option to do what they want. The system's job is to inform that what they are doing is using battery. If a user is OK with it, the system SHOULD NOT interfere.

ex3ndr 6y ago
Using such information is so hard that almost impossible. I could spend a year tailoring battery performance for a messenger and still get random guy who have some exotic phone with some strange behaviour. There are really almost no need to run app in the background or at least constantly send data without a reason (mostly just tracking). UPD: When deciding how to build something i have one small trick: first ask question about who can make better decision about something? For example? Who is more capable to make decision about battery usage, about tweaking core performance, etc? It is obviously kernel or silicone itself. App will never have required information to build perfect performant app for every device. This just means that you have to build a kernel by yourself and even more: common kernel for every phone.
- Andrew_nenakhov 6y ago
  > Using such information is so hard that almost impossible. Aren't battery stats not enough for you? If your app uses too much battery, you can stop using it. Or you prefer some other people to make this decision for you?