3 ms·
I mean, but if the device notifies you that it's running low on battery... maybe you should close the app? Shouldn't this be enough? You would avoid loosing da
by vmateixeira 10y ago
I mean, but if the device notifies you that it's running low on battery... maybe you should close the app? Shouldn't this be enough?
You would avoid loosing data, and regarding user experience, also avoid a slower performance of your app (and perhaps complaining about it?), and also seeing your device shutting down itself with your app screen running in background (which is pretty lame).
- DougWebb 10y agoAs a user, maybe that should be enough. Maybe not. It depends on the app and how critical the data/state is, I guess. As a developer, trying to implement requirements set by a product designer/owner who thinks saving the data is critical even if the user doesn't cooperate, the api is useful to have.
- vmateixeira 10y agoMaybe a critical app shouldn't be web based? If you're really worried about your battery running low and working with critical data, removing the browser overhead which is draining you battery should be one of the first things to do.