immersive-web / immersive-web/depth-sensing
Early feedback request for the API shape
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 57
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Hey all,
I'd like to ask people to take a look at the initial version of the explainer and let me know if there are any major problems with the current approach (either as a comment under this issue, or by filing a new issue). I'm looking mostly for feedback around API ergonomics / general usage, and possible challenges related to implementation of the API on various different kinds of hardware / in different browsers / etc.
+@toji, @thetuvix, @grorg, @cabanier, @mrdoob, @elalish
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read explainer.md first, then review the proposed API shape for ergonomics and implementation challenges across hardware and browsers. Done means recording concrete feedback in this issue or filing focused follow-up issues; the payload does not identify a specific code change or test.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100