Re: [battery] Add an explicit use cases and requirements section (#25)

More use cases:

> * on low power, a video playing site could switch to a less resource-intensive video codec/lower resolution
> * on low power, games could reduce their frame rate or turn off optional features (maybe not every NPC needs full-power AI, for example)
> * on low power, a well-behaved publisher could tell advertisers not to send video ads, only still ads
> * on low power, a document, video, or image processing web app could simplify certain features, such as turn down ML-powered grammar checking, simplify video/image previews, reduce transparency/complex visual effects in the UI, et c.
> * on low power, a publisher could switch layouts from expensive, radio-burning, and reflow-heavy (washingtonpost.com) to something more simple, like text.npr.org

via https://bugs.chromium.org/p/chromium/issues/detail?id=661792#c49

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at https://github.com/w3c/battery/issues/25#issuecomment-1027316300 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 1 February 2022 21:43:43 UTC