Hz Android 2D Porting

Android 2D App Porting to Horizon OS

When to Use

Use this skill when:

• Porting an existing Android 2D app to run on Meta VR headsets
• Adapting a mobile Android app for Horizon OS panels
• Troubleshooting input, layout, or compatibility issues with a 2D app on Meta VR devices
• Preparing an Android app for Horizon Store submission
• Evaluating whether an existing Android app is compatible with Horizon OS

Overview

Horizon OS is built on Android (AOSP) and can run standard Android applications inside panels -- floating 2D windows positioned in 3D space. Most well-built Android apps work on Meta VR devices with minimal changes, but several areas require attention:

1. Input: There is no touchscreen. Users interact via controller pointer (ray-casting), hand tracking, or connected peripherals.
2. Layout: Apps run in resizable panels, not full-screen on a fixed display.
3. Compatibility: Dependencies and permissions must work without Google Play Services or unavailable hardware.
4. Design and performance: Apps must meet Horizon Store requirements on mobile hardware.

The goal of porting is to make the app feel native to the Meta VR experience while preserving existing functionality.

Porting Workflow

Step 1: Initial Testing

Build and install the existing app with its normal Android workflow. Android Studio, Gradle, and adb all work with a connected Meta VR device:

./gradlew installDebug
adb shell am start -n com.example.yourapp/.MainActivity

Prefer metavr app install <apk> and metavr app launch <package> over raw adb here, then stream metavr adb logcat --follow during this first run. Note any immediate crashes, black screens, input problems, or layout breakage.

Step 2: Compatibility Audit

Check whether the app depends on Google Play Services, unsupported hardware, or prohibited permissions before changing its UI. Make unsupported features optional or replace them with Horizon OS alternatives. See Compatibility Requirements.

Step 3: Input Adaptation

The most common porting issue is input. Touch events are translated from the controller pointer, but:

• Hover states are now visible (users point before clicking)
• Scrolling uses the thumbstick, not swipe gestures
• Multi-touch gestures (pinch-to-zoom) do not translate directly
• Tap targets must be large enough for pointer accuracy (48dp minimum)

See Input Adaptation Reference for detailed guidance.

Step 4: Layout Adjustment

Panels are resizable and can have various aspect ratios. Your app must handle:

• Dynamic width and height changes
• Landscape and portrait orientations
• Different effective DPI values

Use responsive Android layouts and window-size breakpoints. See Panel Layout Reference.

Step 5: Gradle and Manifest Updates

Update your build configuration to target Horizon OS:

// build.gradle.kts
android {
    defaultConfig {
        minSdk = 29       // Android 10 minimum
        targetSdk = 34    // API 34 or higher required for all new 2D panel apps
    }
}

Add required manifest entries for device targeting. See Gradle Setup Reference.

Step 6: Input Testing

Test with all supported input methods:

• Controller: point-and-click, thumbstick scroll, trigger tap
• Hand tracking: pinch-to-select, hand scroll
• Keyboard/mouse: Bluetooth peripherals, system keyboard for text fields

Use the Meta Spatial Simulator for rapid desktop iteration, then validate on-device with the Meta Horizon OS Android Studio plugin or normal ADB tooling. Keep metavr adb logcat --follow running during each input pass — it catches input errors that don't visibly crash.

Step 7: Store Submission

Before submitting to the Horizon Store:

• Verify all Compatibility Requirements
• Test on at least Quest 3, Quest 3S, and Quest 2 (if targeting them), plus Meta VR Glasses
• Confirm the app works in both passthrough and immersive home environments
• Review Meta's content policies and technical requirements

Quick Compatibility Check