I am interested in the Lume Pad 2, but one concern I have is the nature of creating software for the device apparently being dependent upon Leia’s proprietary SDK.
Asus has recently release a pair of 3D laptops, and they apparently work with existing standard graphics APIs like OpenXR, Vulkan, WebXR, etc.
Is there anything specific blocking this type of compatibility with the LP2, or just Leia not having the resources to implement it?
The other platforms you mention also have a proprietary SDK and API required to render to their screen.
When it comes to open graphics standards like OpenGL and Vulkan, they are of course supported on Leia platforms already.
Other standards like OpenXR do not yet have approved API bindings for non-VR/AR stereo 3D devices, but we’re more than happy to adopt once they’re available. OpenXR Android apps technically already work on Lume Pad devices, but they’ll simply play back in 2D due to the aforementioned 3D standards not being implemented into OpenXR yet.
WebXR support is a function of the browser. Leia is not a browser company, but if Google Chrome or Firefox or another 3rd party wanted to make a browser version with Leia SDK compatibility, WebXR content would work and Leia would be happy to support it and distribute it on the Leia Appstore.
In addition, 1st party development and code samples and support for these and other technologies may come directly from Leia in the future, especially as they mature and are more widely adopted.
Windows products are slightly different, as all OpenXR executables can connect to any compliant runtime for a device. OpenXR on Android doesn’t work that way (notice how an OpenXR APK for Magic Leap 2 can not play back as an XR app on Pico4).
What would be your desire for OpenXR support specifically? Is there a specific OpenXR app you’d like to port to the platform?
I don’t currently have a specific OpenXR Android app I was interested in, its not something I’ve used since I don’t have a VR device.
I was just bringing it up because I like 3D and would like to see it universally adopted, but if Leia, Asus, Acer, and whatever other manufactures start making 3D devices all have a dozen different propietary ways for presenting 3D content, the broad adoption of native 3D in games, videos, etc. is going to be noticeably slower than if everyone was using an Open3D api or something.
Yeah, I agree with this. It’s best if multiple companies can support the same open standards. However, sometimes there needs to be experimentation, especially at the beginning of a new wave. And, from what I understand, there are multiple technologies involved that don’t all work the same. Even for VR, which has been getting popular for like 6 years at least, the standards are just now coming together (and/or not totally finalized), So it takes time.