ReactVR Links and When to Use Them

A short post … In Dec 2016, React got a new feature – ReactVR. This is a version of React with components with integrate with the WebVR JavaScript API and 3D WebGL in the browser. What better way to position your project on dual “cutting edge” coding – WebVR and React?

However, one of the problems I’ve encountered with the Oculus website is tracking down links to developer tools.

Here then, is what you need for React VR!

Documentation for ReactVR:

https://github.com/facebookincubator/react-vr

ReactVR is a competitor to the A-Frame (http://aframe.io) library, in that they both link markup objects to JavaScript code. Your best strategy is to try both. A-Frame is great for prototyping – creating a set of virtual rooms can be done very fast. ReactVR is the best bet for real production code, due to its integration in the React ecosystem.

It’s also worth noting that both ReactVR and A-Frame use Mr. Doob’s THREE.js WebGL library as their base. This is a pretty big library, and greatly increases the payload for WebVR projects. For maximum efficiency and download speed you might want to explore PrimroseVR, which uses only part of THREE, greatly reducing its payload size. Primrose doesn’t have a markup/XML layer, but does have good support for 3D, audio, and multiuser rooms.