Pico XR Integrations in 2026: A Tour of the Official GitHub Support Repo

If you are evaluating Pico as a development target, the first place to look is not the developer portal but the official support repository at github.com/picoxr/support. It is not the SDK itself — those live in their own downloadable packages — but it is the canonical catalogue of integration patterns, demo projects, and reference implementations. As of July 2026 the repository carries 520 stars, 52 forks, and 59 commits. The low commit count is worth flagging up front: it suggests modest ongoing maintenance, and you should pin your references to specific commits rather than assume the demos track the latest SDK releases.

Four SDK Surfaces, Four Subdirectories

The repository is organised by SDK surface. Each demo is its own sibling repository that this support repo links out to. The split mirrors how most XR vendors package their tooling in 2026: a Unity-native SDK, an Unreal-native SDK, an OpenXR plugin layer for Unreal, and a C/C++ native OpenXR runtime.

Surface	Target	Best for	Repo pattern
PICO Unity Integration SDK	Unity 2022+	C# developers, game studios, content teams	MicroWar, Motion-Tracker-Leg-Tracking, FaceTrackingDemo, Overlay-Demo-UnityXR, EyeTrackingDemo, VideoPlayer-UnityXR
PICO Unreal Integration SDK	Unreal 5.4+	UE studios, platform-service integrations	UIInteractionDemo, HandTracking, PICO_UE5_BodyTrackingSample, PlatformSDK_LeaderBoard-Achievement_UE4, Haptic, RenderingTechniques
PICO Unreal OpenXR Plugin	Unreal 5.4 with OpenXR	Cross-vendor XR pipelines, OpenXR-conformant projects	PICO_UE5_OpenXRSample
PICO Native OpenXR SDK	C/C++	System-level integration, custom runtimes, low-overhead apps	OpenXR_Demos, OpenXR_VideoPlayer_Demo

The Unity surface is the most extensive. Twelve plus demo repositories cover the full feature surface: body tracking via the 3DoF Motion Tracker leg accessories, face tracking, overlay rendering through the VR Compositor Layers feature, eye tracking, screenshot capture, native video player, real-time communication for multiplayer, PlayFab and Photon integration for matchmaking and leaderboards, and VRTK tutorial scenes (a VR bowling game and a farm yard example) for developers using the VRTK v4 spatial computing suite.

The Unreal surface is narrower but covers the high-value platform services: identity and friend list APIs, real-time communication for voice chat, achievement and leaderboard wrappers (updated to UE 5.6 as of mid-2026), broadband haptic feedback, and a rendering techniques sample for the common UE XR patterns.

Enterprise Demos

The enterprise section of the repository targets PICO 4 Enterprise, PICO 4 Ultra Enterprise, and the PICO G3. These are the devices that show up in location-based entertainment (LBE), training simulations, and kiosk deployments — the segments where ByteDance is pushing hardest outside the consumer gaming market.

Demo	What it proves
Launcher-Demo-UnityXR	Custom system launcher replacement — required for kiosk mode
FeaturesDemo	All-in-one showcase of PICO 4 / Ultra Enterprise capabilities
PICOCast	PICO's proprietary casting protocol for sharing the headset view to external displays
ArUcoMarkerTracking	Fiducial marker tracking for AR overlays and tracking-anchored content
Advanced-Guardian-Example	Advanced Guardian LBE mode for multi-player scene scaling
AdvancedEyeTracking	Eye tracking data pipelines on PICO 4 Enterprise
VideoPlayer-UnityXR	4K 3D video playback for training and simulation
CompanionApp	(Coming soon) VR-to-smartphone companion application
GetCameraFrame	Stream PICO 4 Enterprise camera feed to Azure AI services
OpenXR_CloudXR_Client_Demo	NVIDIA CloudXR client built on the PICO OpenXR SDK
Unreal-Engine-LBE-demo	Simple UE LBE demonstration

The GetCameraFrame and OpenXR_CloudXR_Client_Demo entries are the most strategically interesting. Camera-frame streaming to Azure AI is the path Pico is opening up for on-device computer vision workloads — the kind of thing that matters if you are building AR guidance systems or computer-vision-assisted training. CloudXR is NVIDIA's protocol for streaming GPU-rendered scenes from a server farm to a thin client, and having a Pico-specific reference implementation lowers the bar for high-fidelity LBE installations.

Legacy Android Helper Layer

Under the heading "PICO Android Sample Code/JAR File (Legacy)" sit four older repos that predate the OpenXR plugin push. The AndroidHelper repo ships a .jar file that Unity and Unreal projects can use to access and control PICO devices at the Android level — launching system apps, querying package names, and starting the WebVR browser with a specified URL. The LauncherWebVR demo is the de facto bridge pattern for native apps that want to surface WebXR content: spawn the PICO Browser, point it at a URL, and let the user land inside an immersive web session.

PicoPlayManager shows how to launch PICO's built-in video player with a video file path. PackageNameManager retrieves the list of installed packages on the device — useful for kiosk mode where you want to restrict which apps the user can run.

Strengths and Weaknesses of the Repository Pattern

The split-into-many-repos approach has a clear upside: each demo is a small, focused project you can clone and inspect without pulling hundreds of megabytes of unrelated code. The downside is the maintenance signal. 59 commits across this many linked repositories suggests that not every demo is being kept in lockstep with SDK releases. When you build on top of one, pin to a specific commit and validate against the SDK version you ship with.

The other weakness is discoverability. There is no monorepo, no central changelog, and the support README is the only index. New developers frequently miss the LauncherWebVR and AndroidHelper patterns because they are filed under "Legacy" and look deprioritised, when in practice they are still the recommended bridge for native-to-web scenarios.

Which Demo to Read First

If you are new to Pico development and you are a Unity shop, start with MicroWar. It is explicitly described as an "all-in-one demo that meticulously showcases the core features of the PICO Unity Integration SDK" and gives you a working reference for the platform services layer (accounts, friends, achievements) plus input mapping and rendering.

If you are an Unreal shop, start with UIInteractionDemo and HandTracking. The former is the canonical controller-to-UI mapping sample; the latter is the canonical hand-tracking implementation. After that, move to PlatformSDK_LeaderBoard-Achievement_UE4 for the platform-services story.

If you are building cross-vendor XR with OpenXR, go straight to PICO_UE5_OpenXRSample for UE5 or OpenXR_Demos for native C/C++. These are the surfaces least likely to drift as Pico's proprietary SDKs evolve, because they conform to the Khronos OpenXR spec.

If you are doing enterprise or LBE work, FeaturesDemo and Advanced-Guardian-Example are the highest-signal entry points. The OpenXR_CloudXR_Client_Demo is the right starting reference if you intend to stream GPU-rendered content from a server.

Support Channels

For issues that go beyond what the demos can answer, the support contacts are: pico_devsupport@bytedance.com for general developer support, pico-business-techsupport@bytedance.com for enterprise customers, and the support portal at picodevsupport.freshdesk.com. The Discord is also active and is a faster path for community questions.

The repository is, ultimately, a curated index of integration patterns rather than a working codebase. Treat it as a map of what is possible on Pico in 2026, and use the linked sub-repositories as your actual point of departure.