Contact

Get in touch

The fastest way to reach me is email: [email protected]. I read everything, and I reply to most things.

Corrections are especially welcome

If a demo behaves differently on your headset, if a support matrix is out of date, or if an explanation is simply wrong, please tell me. Include the device, browser, and browser version if you can — WebXR behaviour varies enough between runtimes that those three details usually determine the answer.

Compatibility claims on this site carry the date they were checked, which is an admission that they go stale. A report that a stated behaviour no longer matches a current runtime is the most useful mail I get, because it is the kind of error I cannot find on my own hardware.

What I can and cannot help with

Questions about something written on a page are welcome, including the ones that amount to "this paragraph did not make sense to me" — that is a defect in the writing and worth knowing about.

Debugging your own application is outside what I can do by email. There is rarely enough in a description to identify the problem, and the answer almost always depends on the device. A minimal reproduction posted to the WebXR community or to the three.js forum will reach people with a wider range of hardware than I have.

Reusing what is here

The code samples are written to be copied. Take them, adapt them, ship them; no attribution is required and none is expected.

For the written explanations and the demos, please link rather than republish. If you want to translate a page, or use one in teaching material, ask and the answer will almost certainly be yes.

Response time

This site is maintained by one person alongside other work, so a reply can take a few days. Corrections get acted on faster than they get answered: if you report something wrong, the page may well be fixed before you hear back.