So I tried to port my app to Android XR 🕶️
summary
Porting an app to Android XR proves feasible but partial: a 90% Compose codebase lets panels and orbitals ingest existing composables quickly, but lack of adaptiveness and multi‑activity architecture breaks spatial continuity. Work happens in the emulator only, using Android Studio canary and the XR SDK (alpha 12), with experimental Compose XR panels, resizable subspaces, and a prototype three‑panel layout that mostly runs yet crashes on activity transitions. Also demos Compose XR and Glimmer SDK.
AI-written summary · about
chapters (10)
- 0:00Android XR porting journey
- 1:05What is XR
- 4:42XR evolution at Google
- 8:37Designing XR UX
- 16:49First XR project setup
- 22:08Porting Air Console to XR
- 32:54Porting key takeaways
- 36:43Glimmer SDK for AI glasses
- 39:34XR developer resources
- 40:16XR devices Q&A
related talks
43mSo I tried to port my app to Android XR 🕶️
21mExtending Android XR’s Reality
32mPrepare for Android XR with Quick Wins and Powerful Features
22mBuild 3d experiences using Jetpack XR
22mModern Android Development #AskAndroid
29mAdapting Android Apps for Multiple Screens Compose-First Approach
51mShared mobile UIs with Compose Multiplatform- 22mBuild 3d experiences using Jetpack XR