GDC’s annual State of the Game Industry survey of developers is out ahead of the 2019 Game Developers Conference in March and it offers some some new data about developer sentiment relative to the VR/AR market.
You can check out last year’s report here showing Vive continues to drive the most interest among developers. On this year’s survey, the question “Which platform(s) are you *currently developing* games for?” saw 33 percent of VR/AR developers pick Valve/HTC followed by Rift at 30 percent. In addition, though, 21 percent of VR/AR developers said they were working on the still unreleased Oculus Quest. Developer kits for the $400 Quest aren’t available publicly so it’s a notable showing for the standalone VR system ahead of its launch. I should also add that the “Other” category was also selected by 42 percent of VR/AR developers.
One other key question in the survey, which allows for multiple answers, asks “Which VR/AR device(s)/platform(s) most interest you as a developer right now?” Valve/HTC also leads in that category, with 36 percent, though Quest still made a strong showing with 22 percent of respondents picking the headset.
Below are the answers to this same question over the last three years.
2019
2018
2017
AR vs. VR
On another question, only 17 % of developers said they are currently working on VR headsets. That’s 10% more than game developers currently working on AR headsets. Likewise, 14 percent of developers said they anticipated their next game would be released on VR headsets while only 6 percent said the same of AR headsets.
Another question, though, tried to get developer sentiment over the long view, with 34% believing AR would be the dominant “immersive reality” technology in five years. That’s compared with 19 percent for VR.
You can check out the survey yourself by filling out the registration form on the GDC site.
Tagged with: GDC, State of the Game Industry, survey
The post GDC 2019 Survey: 33% Of VR Devs Working On Vive, 21% On Quest appeared first on UploadVR.
from UploadVR http://bit.ly/2CHLcPW
via IFTTT
No comments:
Post a Comment