사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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.