[w3ctag/design-reviews] WG New Spec: WebXR/WebGPU integration (Issue #1298)

toji created an issue (w3ctag/design-reviews#1298)

### Specification

https://immersive-web.github.io/webxr-webgpu-binding/

### Explainer

https://github.com/immersive-web/webxr-webgpu-binding/blob/main/explainer.md

### Links

- The WG's request for this TAG review: https://github.com/immersive-web/webxr-webgpu-binding/issues/43
- Previous early design review, if any: https://github.com/w3ctag/design-reviews/issues/####
- An introduction to the feature, aimed at unfamiliar audiences: https://github.com/immersive-web/webxr-webgpu-binding/blob/main/explainer.md
- A description of the problems that end-users were facing before this proposal: WebXR content demands high performance rendering, and WebGL isn't always able to meet developers performance goals. The WebGPU API is designed to minimize the type of overhead that could hamper WebGL content, which should make it an ideal target for WebXR developers.
- Alternatives considered: There are no viable alternatives to consider, given that the entire point of this spec is to add interoperation between two APIs.
- Examples of how to use the proposal to solve the end-users' problems: Giving WebXR developers access to WebGPU allows for faster rendering, better balancing of CPU/GPU work through compute shaders, and forward mobility with an API that isn't in maintenance mode.
- What do the end-users experience with this proposal: https://github.com/immersive-web/webxr-webgpu-binding/blob/main/explainer.md#webgpu-binding
- User research you did to validate the problem and/or design, if any: Discussion was done with both the WebXR and WebGPU working groups, and feedback was solicited from developers when the feature was made available behind a flag. Developer feedback has generally been a tone of eager anticipation.
- Web Platform Tests:  https://immersive-web.github.io/webxr-samples/webgpu/


### The specification

- [x] Follows the [Web Platform Design Principles](https://www.w3.org/TR/design-principles/).
- [ ] Includes Security and Privacy Considerations sections based on answers to the [Security/Privacy Questionnaire](https://www.w3.org/TR/security-privacy-questionnaire/).

### Where and by whom is the work is being done?

- GitHub repo: https://github.com/immersive-web/webxr-webgpu-binding/
- Primary contacts: 
  - Brandon Jones (@toji), Google, Spec Editor
  - Rik Cabanier (@cabanier), Meta, Implementer/Spec consultation
  - Mike Wyrzykowski (@mwyrzykowski), Apple, Implementer/Spec consultation
- Organization/project driving the specification: Apple, Meta, Google
- This work is being funded by: Apple, Meta, Google
- Primary standards group developing this feature: Immersive Web Working Group
- Incubation and standards groups that have discussed the design:
  - Immersive Web Working Group
  - WebGPU (https://github.com/gpuweb/gpuweb/issues/2778)


### Feedback so far

- Active horizontal reviews:
- Multi-stakeholder feedback:
  - Chromium comments: Supportive
  - Mozilla comments: None. Mozilla is not implementing any Immersive Web specs.
  - WebKit comments: [Shipped on Vision Pro](https://developer.apple.com/documentation/safari-release-notes/safari-26_2-release-notes#Spatial-Web)
  - Meta: Shipping soon on Meta Browser
- Major unresolved issues with or opposition to this specification: None. Some secondary features still under discussion such as how to enable foveated rendering.
- Status/issue trackers for implementations:
   - [Chrome Status](https://chromestatus.com/feature/5077077997649920)
   - [WebKit](https://developer.apple.com/documentation/safari-release-notes/safari-26_2-release-notes#Spatial-Web)


### You should also know that...

_No response_

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1298


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

Message ID: <w3ctag/design-reviews/issues/1298@github.com>