Request for System Wake Lock use cases

[anssiko]

Following the announcement to split the wake lock capability into two, the Devices and Sensors WG is soliciting the System Wake Lock API use cases to ensure the spec work started in 2015 addresses the right use cases the right way.

Anyone can help (including folks who are not participants of the group) by opening a new issue in this repo describing their use case(s) they feel cannot be realized without this capability.

Here's example use case input:

• Background geotracking use case (1, 2)
• Fitness App #2 by @CheloXL
• Transfer learning #5 by @irealva

With more such compelling use cases at hand the group is committed to reinvigorate the spec work in its scope and collaborate with browser vendors to ensure their perspectives are considered.

Before the actual spec work, the group may write an explainer (example) that synthesizes this input from various stakeholders and guides the actual spec work.

[hadriann]

Maybe it is worth mentioning what the System Wake Lock is and does. And if it has anything to do with the GPS of the device, so that we don't end up with use cases that are not applicable to this spec. Background geolocation is a feature so common in native apps on mobile devices that it needs no introduction or use cases. But it is not clear yet if background geolocation should be made possible via System Wake Lock or via Geolocation Sensor API.

[reillyeon]

At a high level the idea of a system wake lock is that it allows a page to continue to do work in situations where the system would otherwise enter a low power mode. I'd like to solicit a wide range of use cases, background geolocation being only one. The interactions between the system wake lock concept and other APIs are interesting to explore. I'd like to hear about use cases that involve something other than geolocation to understand the wider space of developer needs.