[Someone]

So, you want to develop an AR/VR device, and start shopping for hardware.

You’re not a mega company (yet), wanton get to market fast, so you want to focus on the AR/VR features, not on getting an OS, drivers and libraries for (3D) graphics up and running. You also want something (somewhat) portable, and assurance that you still can get hardware to deploy your stuff on X years from now.

You also don’t want to order a million units up front.

Given those constraints, I think you’ll find Android is your best option.

[george3d6]

> You’re not a mega company Right, I'm asking why Steam, HTC and Meta did this, which are in the top <x> tech companies by market cap and spend billions on this stuff. Totally get why a small VR device dev would not do this.

> OS, drivers and libraries for (3D) graphics up and running Right, except that I am not saying one should build a kernel, and webgl, cuda, etc are kernel dependant not OS dependant

> assurance that you still can get hardware to deploy your stuff on X years from now I am unaware of android-specific hardware features to date (linux specific, maybe, but not android) -- you can literally add any bootloader and load a linux kernel and get drivers running on most phones even, w/o android, and where "android" is necessary it's simply an artifact of the company maintaining the phone having build the drivers into their distro and not released them separately.

> You also don’t want to order a million units up front. Again, seems unrelated, I'm talking about building the VR hardware i.e. not order off the shelf and white label (unless your claim here is that meta, htc, steam etc are doing white labeling, which doesn't seem to be the case)