# AR and VR Development on Android: A Practical Guide *Published:* 2026-02-22 *Author:* Steven Jacob Android AR and VR looks dramatically different from the 2022 ARCore era. Android XR (the Samsung Galaxy XR headset launched late 2025 and the Pixel XR coming mid-2026) is now the headline platform, ARCore for handheld AR has matured into a stable but secondary surface, and the WebXR story has continued to lag despite repeated revivals. For developers, the practical question is which surface to target and what stack to commit to. Below is the current 2026 picture: where each surface is genuinely worth building, which engines and frameworks to pick, and what to watch out for. ### TL;DR **The pick:** For Android XR headset apps, target Android XR (formerly project codename) with Jetpack XR Compose or Unity. The Samsung Galaxy XR and incoming Pixel XR share a runtime. **Runner-up:** For handheld AR on Pixel and Galaxy phones, ARCore Geospatial API and Scene Semantics. Stable but a secondary surface; expect modest install bases. **Skip if:** Skip VR-only on Android phones (Cardboard-style) entirely. The category is effectively dead; the audience has moved to dedicated headsets. The 2026 Android XR landscape ----------------------------- Android XR is Google and Samsung’s joint runtime, launched at the end of 2025 on the Samsung Galaxy XR headset, with the Pixel XR expected mid-2026 at a lower price point. The runtime supports both VR and passthrough AR on the same hardware, with the Quest 4 and Apple Vision Pro as the main competition. Jetpack XR Compose extends Compose Material 3 to spatial UI, with new primitives for panels, volumes, and spatial layouts. The development model is closer to building a tablet app with spatial extensions than building a traditional VR app from scratch in Unity, which materially lowers the bar to entry for Android-native teams. Picking your engine: Jetpack XR, Unity, Unreal, or Godot -------------------------------------------------------- Jetpack XR Compose is the right pick for productivity apps, content viewers, and apps that share a codebase with phone and tablet. Native Android skills transfer directly. Unity remains the right pick for games and immersive 3D content. Unity 6 has solid Android XR support; the asset pipeline and ecosystem advantage is decisive for game work. Unreal Engine 5 is competitive for high-end content but has weaker Android XR adoption than Unity. Godot has early Android XR support; viable for indie and small-team projects. ARCore for handheld AR ----------------------- ARCore Geospatial API (street-level AR anchored to Google Maps) is the most differentiated capability. Cities like London, San Francisco, New York, Tokyo, and Singapore have dense coverage. Use cases that work: way-finding, location-based games, real estate previews, retail try-ons in flagship store locations. Scene Semantics (object and scene recognition on the live camera feed) has matured. Useful for AR shopping (recognize a product on a shelf), accessibility (real-world OCR), and entertainment. Expect modest install bases for ARCore-only apps; the killer use case still has not emerged. Spatial UI patterns that work on Android XR ------------------------------------------- Anchored panels (UI floating at a fixed world position) for productivity and content viewing. Body-anchored panels (UI follows the user with a slight lag) for tools and controls. Hand-anchored panels (UI attached to a hand or wrist) for quick access. Mix and match based on the user task. Spatial typography sits between phone and TV: text size 1.5 to 2x larger than phone baselines, generous spacing, high contrast. Hand-tracking interaction is the default; controllers are supported but secondary in the 2026 Android XR design language. Performance and battery: the headset realities ---------------------------------------------- Android XR devices target 90 to 120 hz refresh with foveated rendering. Frame time budgets are tight (8 to 11 milliseconds) and any sustained drop produces visible discomfort. Profile aggressively with the Android XR developer tools (System Trace plus the new Spatial Profiler). Battery is the second hard constraint. The Galaxy XR runs roughly 2 to 3 hours on a charge; the Pixel XR target is similar. Background work, network use, and aggressive rendering all cut battery sharply. Design for short sessions and clean state save and resume. Distribution: Play Store XR plus side channels ---------------------------------------------- Google Play Store has a dedicated XR section, with separate ratings, screenshots, and listing copy from the phone Play Store. App review for XR has its own bar around comfort, accessibility (seated mode, motion sensitivity), and content moderation. Side-loading and developer distribution channels work but limit reach. Most successful XR app launches ride the official Play Store channel; the ecosystem is too young to bypass it. ### Pick the right XR surface for your project - **Productivity, content viewer, code shared with phone or tablet:** Jetpack XR Compose - **Game or immersive 3D content:** Unity 6 - **Location-anchored AR in major cities:** ARCore Geospatial API - **Real-world object or scene recognition:** ARCore Scene Semantics - **High-end visual fidelity for limited platforms:** Unreal Engine 5 **Important:** Android XR is a young platform with a small installed base relative to phone or tablet. Build XR features with a clear hypothesis about why the spatial UI matters; copying a phone app into a spatial UI rarely produces a compelling experience. FAQ --- ### How big is the Android XR market? Galaxy XR is in the low hundreds of thousands of units a year into Q1 2026, with Pixel XR expected to push the combined number into low millions through 2027. Smaller than Quest but comparable in revenue per user for premium apps. ### Does Apple Vision Pro experience port to Android XR? Not directly. The runtimes are different (visionOS plus RealityKit versus Android XR plus Jetpack XR or Unity). Conceptual patterns transfer; code does not. Plan a separate engagement for each platform. ### Is WebXR a viable target? Marginal. Chrome on Android supports WebXR but the experience is materially worse than native; Safari on visionOS has limited WebXR. Use for prototypes and lightweight content; do not bet a product on it. ### What about hand-tracking versus controllers? Android XR defaults to hand-tracking on both Galaxy XR and Pixel XR. Controllers are supported as an accessibility option and for specific game genres. Design hand-first; support controllers as a secondary. Where AR and VR development lands in 2026 ----------------------------------------- Android XR is the most interesting new development surface in years. The platform is young but credible, the development model favors Android-native teams, and the early app ecosystem has plenty of room. Pick the right engine for your project, design with spatial UI patterns from the start, and treat battery and performance as first-class constraints. Get those three right and the platform’s growth and 2027 becomes a real opportunity rather than a distraction. #### How we put this guide together The picks and steps in this guide reflect what works on current Android builds. Our editors test apps on Pixel 8a and Galaxy S24 hardware running Android 15 and Android 16, cross-check against vendor documentation, and update each guide when behavior changes. ### Related on BestForAndroid - [How to Play Bingo on Android: A Practical Guide](https://bestforandroid.com/how-to-play-bingo-on-android-a-step-by-step-guide/) - [Top Android Development Agencies: A Hiring Guide](https://bestforandroid.com/dev/top-android-development-agencies/) - [How to Hire the Best React Developers: A Practical Guide](https://bestforandroid.com/dev/how-to-hire-react-developers/) - [How to Pick a Good Instagram Username: A Practical Guide](https://bestforandroid.com/instagram-girls-names/)