Re: [w3ctag/design-reviews] Web page settings to save battery (#546)

> @torgo, @LeaVerou, @rhiaro and me looked at this in our TAG Virtual F2F breakout
> 
> We believe we understand the video conferencing use-case now. Some sites get very quick user interaction and probably won't like to be throttled (A), but other sites like video conf would knows that their users have another hour of meeting left and they are low on battery so they may want to optimize for the battery to last as long as possible and hopefully until the meeting is over (B).

Yep, that's it. Some sites really want smooth and fast performance, and some would prefer an extra hour of battery life over super-smooth animations. And the browser can't easily guess which is which.

> For (A) we think an opt in or opt out won't work, but instead a priority might, like you are going to get throttled so what matters the most to you, high framerate, background tasks, foreground tasks? Then the browser can consider those hints

I think these use cases go into the category of: what to do when there is low battery or a user signal to use fewer resources? Anyway, +1 to your point here.

> For (B) an opt in might work, but we think an event that low battery mode is active makes more sense, then the vidconf site can lower video resolution etc and turn off live captions and many other things to save battery.

Consider this situation: User enters a video conferencing site with battery at 100%, and stays on the call for multiple hours. The user would like to extend the length of the call. The best way to do so may be to save battery life along the entire timeline of the call, not just near the end when the battery is getting low.

I don't think the event you suggested would work for this case.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/546#issuecomment-775357112