Meta Extension describes spatial keyboard with template, animation and text context. See benefits, limits and risks of portability.

Direct answer

The OpenXR `XR_META_virtual_keyboard` extension defines resources for creating and positioning a virtual keyboard, loading model and texture, applying animations, providing text context, and receiving interaction by hands or controllers. It is a Meta extension and not a Khronos-ratified extension, so its availability depends on the runtime. For XR products, the value is in standardizing integration across the supported ecosystem while maintaining fallback and testing for privacy, accessibility, and portability.

Model and behavior are coordinated

The API brings together geometry, texture, animation, and state to avoid fragmented integrations.

Text context calls for minimization

Field information can be sensitive; share only what is necessary and do not log content by default.

Hands and controls expand input

Ray and direct touch meet different scenarios, but they need targets, feedback and error correction.

Vendor extension limits reach

Support must be consulted at runtime and accompanied by alternatives for other runtimes.

Nexus Reading

Adopt by capability, not assumption, and validate language, ergonomics, privacy, and fallback on target hardware.

FAQ

Is the extension part of the OpenXR core?

No. It is an extension of the Meta and is not ratified by Khronos.

Does it support hands and controllers?

The specification provides for direct and ray input sources.

How to maintain portability?

Consult runtime support and offer an alternative input method.

Essential guides to delve deeper into the decision

Primary sources and references

This editorial analysis was produced by Nexus from the official sources below, consulted on October 4, 2026. The text is original and interprets practical implications for companies.

Date reported by main source: official specification verified on October 4, 2026.