3 ms·
The irony being that Android is the one whose SDK has a hell of a lot of support for this sort of suspension and recovery.
by rtpg 4y ago
The irony being that Android is the one whose SDK has a hell of a lot of support for this sort of suspension and recovery.
- makushenko 4y ago[flagged]
- fingerlocks 4y agoiOS has just as much support for this too. It’s built into the default constructor for all UI elements, but most devs just ignore it.
- deleted 4y ago[deleted]
- olliej 4y agoThe app switching model for iOS apps has been “expect to be killed at any time” from day 1. The APIs and such are built into almost everything and everywhere it is relevant, because that is the iOS model. Terminating an app that isn’t being used is always better for battery life and system performance. Doing that well has been why iDevices have always had less ram than equivalent generation android devices. The problem is the increasing number of giant custom “cross platform” apps, that require vastly more ram, and have never put any effort into actually being good software. Given all the BS reasons apps get rejected from the App Store the fact that not handling sudden termination isn’t something that gets apps rejected is obnoxious.