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

What might also be useful is turning the use cases into a three column table: use case, examples and type (kiosk, extension, web apps), alternative solution (e.g., MMS). That would allow us see gaps. What's key here is that there may be places where the API is being used that is either *ideal* (a battery indicator?) or *not ideal* (e.g., media loading - where a better solution exists or could be standardized). 

-- 
GitHub Notification of comment by marcoscaceres
Please view or discuss this issue at https://github.com/w3c/battery/issues/25#issuecomment-2148585260 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 23:42:25 UTC