- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2017 11:41:16 +0000
- To: public-device-apis-log@w3.org
It seems the use cases I [documented a while ago][1] are relevant here, adjusted slightly to map to the power saving mode: * App adjusts the amount/number of messages/tweets/data it fetches over the network as well as the polling frequency depending on the power saving mode state. If the user has put the device in power saving mode, the app will only poll for new data if the user explicitly interacts with the app and clicks the "Update" button. If the power saving mode is turned off, the app fetches data without user interaction. * App will only start an expensive (in terms of battery) operation that must run to completion if the device is not in power saving mode. For example, show a simpler map and not the fancy WebGL one if in power saving mode while using a web-based navigation app. (the navigation app knows how long it'll take to get to your destination, so can act accordingly). * App will only start a long-running irreversible operation if the power saving mode is turned off. For example, a very tedious checkout process, or an update of app assets (e.g. download of hi res textures for the new level in a web-based game). The [Web Budget API][2] could be relevant to this discussion, but it is scoped to background operations. (cc @beverloo @riju) [1]: https://lists.w3.org/Archives/Public/public-device-apis/2016Jul/0011.html [2]: https://wicg.github.io/budget-api/ -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/battery/issues/9#issuecomment-285329530 using your GitHub account
Received on Thursday, 9 March 2017 11:41:22 UTC