The purpose of this blog is to share ideas, collaborate and gather feedback on technical experiments around the use of Virtual Reality for data analytics and business applications in general.
With the recent revival in VR hardware and the general availability of APIs and 3D application development environments, Virtual Reality is in everbody's grasp, so we might as well give it a try to see what we end up with!
Since there's too much choices to be made, we might as well make them upfront. We'll deal with their potential limitations later on. If we're to visualize data in virtual reality we're going to need a couple of things:
- We obviously need the hardware. This choice is going to become a lot more difficult in the near future I'm guessing, but for now let's go for the guys that foster experimentation: Oculus it is (https://www.oculus.com/)
- We're going to need a development environment. One that supports the API of Oculus obviously. I haven't tried the other one yet so Unity it is (http://unity3d.com/)
- We'll need to consume data from external sources. Preferably in a standardized & harmonized manner. A nice, simple, open, singular protocol would be nice. It would be awesome of course if it supports classic analytical operations (like querying, filtering, navigating between objects etc..). I hear you, to hell with web services, we're going for OData (http://www.OData.org/)
- It's going to have to look really really awesome (eventually), so we might as well include a 3D design studio. One that is free for example (http://www.blender.org/)
And the way we go! Wait.. I've got a nice stupid picture to bring it all together with logos and stuff:
Admit it, you're impressed! Notice the sleak, minimalistic m$ pp design, the obvious google imagery, the distressing... whatever, you get the idea.
More to come..