The research behind
ReactVision's AR and VR stack
Labs is where we publish the R&D that sits next to, and underneath, our products. Some of it already runs inside ViroReact, Studio, and Platform. Some of it is adjacent to XR altogether. All of it is work we think is worth showing.
Projects
One page per project, with what it is, where it is used today, and where to follow the work.
Eskiu, the self-hosting systems language inside ReactVision's AR engine
A statically typed systems language that compiles to native code through LLVM, with explicit memory, direct C interop, and no garbage collector. Rendering modules in the ViroCore engine behind ViroReact have moved from C++ to Eskiu and use about 85% less memory. MIT licensed.
ReactVision Spatial, the services that make a place persistent and shareable between devices
The spatial layer behind ViroReact: cloud anchors, room-scale scans, geospatial anchors, a live co-location channel, and replicated application state. Written in C++ with ReactVision's own vision pipeline, no external vision libraries and no Google dependencies, and shipped inside the ViroCore engine.
What belongs in Labs
Research, not roadmap
Labs projects are R&D. Some are already in use inside our engine, others are experiments. None of them are product commitments, and each page says plainly what stage the work is at.
Adjoining XR, not always inside it
A programming language, a tracking pipeline, a port to hardware nobody expects. The work here sits next to AR and VR, and often underneath it, rather than being an AR or VR feature itself.
One stack, our own
Owning the layers beneath ViroReact, Studio, and Platform is what lets one codebase reach phones, headsets, and the browser. Labs is where that ownership gets built and tested.
Working on something adjacent?
If you are building on the layers beneath XR, or want to put one of these projects to work, we would like to hear about it.