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

Two things:

1. Please ensure that the applications are distinctly categorized as a) *kiosk mode*, b) *browser extensions*, and c) genuine *web applications*. It's important to recognize that kiosk modes and, in particular, **browser extensions** operate under security models different from those of regular web pages. As previously discussed, while it might be appropriate to expose the API in these controlled environments, suggesting that its use in a browser extension justifies broad web exposure is misleading. This is akin to claiming that old 'Cordova apps' qualify as standard implementations, when we know those are not "web applications" in the HTML sense.

2. About the YouTube case (and also the browser extensions doing source selection): The selection of media based on battery status presents a valuable discussion point, but lacks sufficient consideration of varying network conditions and hardware capabilities. A more robust solution is offered by the [Managed Media Source API](https://www.w3.org/TR/media-source-2/#dom-managedmediasource), which allows the browser to more effectively manage the media source. Unlike the battery-based approach, this API incorporates a broader spectrum of environmental factors, including available hardware and network conditions. The implementation of this API enhances system efficiency by reducing power consumption, improving memory management, minimizing buffer requirements, and facilitating access to 5G connectivity. Furthermore, it maintains developer control, ensuring flexibility and adaptability in media handling. To simply, with the availability of the Managed Media Source, which was developed together with large video sites, developers don't need to the Battery API for source selection through JS: the browser does it better/much more intelligently and efficiently.


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


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

Received on Tuesday, 4 June 2024 10:30:30 UTC