New in Immersive Web SDK 1.0: your coding agent can now run and test your app itself, either in the desktop emulator or on a Meta Quest connected to your computer. It finds the slowdowns your users would hit before they do. Start building with IWSDK 👉

Test real journeys. Measure against explicit thresholds. That's how regressions get caught

Letting the coding agent run and test on an actual Quest is the part that matters. My setup hands code to Cursor, and the biggest win has been when it can verify its own work instead of me eyeballing it after. Curious how it reports perf regressions back.

useful when “slow” is defined per interaction: frame-time budgets, startup limits, or a threshold for controller response. otherwise the agent can spot regressions without knowing which ones users will actually feel.

For each agent-made performance fix, I'd keep a repeatable input path, frame-time trace and matching-view screenshots from before and after. Run both builds on the same Quest/browser version so faster rendering doesn't mask a visual or interaction regression.

Does agent testing work across Quest models or just the one plugged in?