3 ms·
These phones go much farther the already absurd limitations of standard Android ("we know what apps a user doesn't care about so we'll kill them without asking,
by g-b-r 3y ago
These phones go much farther the already absurd limitations of standard Android ("we know what apps a user doesn't care about so we'll kill them without asking, at any time").
Most developers are not aware of them, and in any case it's very hard to constantly save all the state
Hardly any previous system in the history of computers has ever required it, and Android's developer documentation doesn't highlight enough how much it's required.
Most of all it's the fault of these phones' extreme, undeclared, undocumented and absurd behavior anyhow.
- tsukikage 3y agoHardly undocumented! https://developer.android.com/guide/components/activities/process-lifecycle https://developer.android.com/guide/components/activities/pr... The expectation in mobile environments is that you store whatever information you need to resume from cold in response to the app leaving the foreground, since the OS may kill it with little further warning at any time thereafter. This recommendation occurs prominently in the lifecycle docs for both iOS and Android.
- g-b-r 3y agoThe vendors-specific behaviors reported in dontkillmyapp are undocumented