Laptop / workstation
Debian → GNOME → 3DVR
Use the mature desktop for demanding work while 3DVR supplies consistent policy and services.
One computing experience across powerful desktops, lightweight machines, phones, and XR— without requiring every device to run the same desktop environment.
3DVR should not depend on GNOME, XFCE, Phosh, or any single shell. Those environments can provide windows, input, displays, power management, and hardware integration while 3DVR provides the experience people actually recognize: identity, apps, agent behavior, device policy, sync, and consistent interaction.
Debian → GNOME → 3DVR
Use the mature desktop for demanding work while 3DVR supplies consistent policy and services.
Debian → XFCE or Labwc → 3DVR
Keep memory and GPU overhead low without creating a second product experience.
Linux → Phosh or another mobile shell → 3DVR
Reuse the same identity, apps, agent, sync, and policies with touch-first presentation.
Linux or browser runtime → 3DVR spatial shell
Use the same core services while three-dimensional interfaces become the primary surface.
Forking a full desktop environment makes 3DVR responsible for years of compositor, accessibility, input, graphics, and hardware maintenance immediately. A portable layer lets us improve the user experience now, upstream fixes where possible, and only replace components when we have a clear reason.
This also keeps 3DVR usable on machines where GNOME is too heavy. The system can scale down without throwing away the agent, apps, account, or product philosophy.
A desktop may expose every audio route correctly and still leave the user managing implementation details. 3DVR can add a simple human rule on top: prefer a plugged-in headset, then an external display, then built-in speakers. The operating system still handles PipeWire and drivers; 3DVR supplies the policy.
keep mature Linux infrastructure underneath; add small, understandable policy services above it; move functionality into 3DVR only when doing so produces a clearer universal experience.
Do not make core 3DVR services depend on one compositor, toolkit, CPU architecture, or vendor cloud.
Fix Linux components upstream when the problem belongs upstream. Keep 3DVR policy focused on product behavior.
Expose choices when they matter. Automate routine hardware decisions when a safe preference is already known.
Start on mature desktops, scale down to tiny systems, and earn the right to replace deeper layers over time.
This architecture connects existing 3DVR work on phones, personal Linux infrastructure, XR interaction, and the broader roadmap.