Hi @cnpsc yes it's describing the problem from the developer perspective rather than from the end-user perspective. It may seem like make-work but we're really trying to emphasize (in the TAG review process) the idea of end-user-centricity - in other words, that people who are working on new APIs for the web are thinking about new functionality from the end-user perspective. Also remember the explainer is not just for TAG review. For example - what you write in the explainer could help ti inform eventual developer documentation (e.g. on MDN). So yes please if you could start with the (end) user need that would be much appreciated. And thanks for the pointer to the discussion with the Web Perf working group - this is exactly the kind of "trajectory" information we are looking for when we review something in WICG or another community group. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/682#issuecomment-1042921996 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/682/1042921996@github.com>
Received on Thursday, 17 February 2022 12:57:15 UTC