by Marty Resnick | August 10, 2017 | Comments Off on Getting Started Developing Virtual Reality Experiences
Understanding the unique technology and process considerations for developing virtual reality (VR) solutions, ranging from 360-degree videos to fully immersed 3D simulations, is a challenge for application leaders and developers. My latest note, “Getting Started Developing Virtual Reality Experiences“, discusses these considerations and provides recommendations for choosing the right VR experience for a specific use case and delivering immersive VR experiences.
Virtual reality is useful for a wide-array, and continually growing, number of use cases and there are no one-size-fits-all solutions. Therefore starting tactically is the right approach. Choosing a specific use case will drive the technology, process, tools, and resources that will be required to deploy a successful VR immersive experience.
When developing VR experiences, there is a growing number of technologies and tools to consider with a growing list of vendors. Our upcoming “Market Guide for Virtual Reality” will provide a deeper dive into those tools and technologies. However, there are also critical items that warrant special consideration including:
- Immersive user experience
- Narrative development/storytelling
- Player/user testing
Although these items are touched upon in the note, these will be themes for some future research moving forward.
In a nutshell, this note introduces the process of defining a Minimum Viable Product (MVP),choosing the right VR experience, inventorying existing skill sets, understanding when its time to bring in subject-matter experts (SME), and decide when its time to build an -in house capability.
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.