使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/meta-quest/agentic-tools --skill hz-metavrx-layout-sdk开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
MetaVrx Layout SDK
Use the Layout SDK when a Standard Android app needs multiple app-owned panels on Meta Horizon OS. It preserves the app's existing Android UI framework. Do not add Meta Spatial SDK unless the app needs an immersive scene, 3D entities, or full environment control.
Choose the framework first
| Existing app UI | API style | Start here |
|---|---|---|
| Jetpack Compose | SpatialScene, SpatialWindow, WindowModifier | Compose setup and Compose API |
| React Native | SpatialSceneProvider, SpatialWindow, props and hooks | React Native setup and React Native API |
The app's UI framework dictates which set of references to continue with. The Jetpack Compose and React Native APIs are intended to strive for behavioral and conceptual parity across platforms.
Mental model
Compose:
setContent {
SpatialScene(
theme = { content -> AppTheme { content() } },
) {
MainScreen()
SpatialWindow(
key = "details",
modifier = WindowModifier
.size(480.dp, 640.dp)
.anchor(WindowAnchor.End),
) {
DetailsScreen()
}
}
}React Native:
import {SpatialSceneProvider, SpatialWindow} from '@metavr/layout-compat';
<SpatialSceneProvider>
<MainScreen />
<SpatialWindow
label="details"
windowWidth={480}
windowHeight={640}
anchor="end">
<DetailsScreen />
</SpatialWindow>
</SpatialSceneProvider>;The main content remains in the app's system panel. Each SpatialWindow declares child content that the compatibility layer can promote into a separate panel when the platform supports it. Read the framework's placement reference for anchoring, semantic offsets, asynchronous promotion, priority, and fallback behavior.
Read what you need
Jetpack Compose
React Native
An installed partner or internal tier may provide additional reference files. Use one only when its filename directly matches the requested capability.
For exact signatures and version-specific availability, use the SDK types and documentation shipped with the dependency, or metavr docs api-search "<Class>" for the indexed API reference.