Google’s annual I/O conference kicks off tomorrow and we’re expecting VR to be a major part of the event. Here’s a look at everything we know and what we expect to see from Google’s virtual reality initiatives.

Android N Bakes in VR

Android was built as an operating system for more phones, not for VR headsets. The latency between input and response that’s acceptable for tapping and swiping is far removed from the sub-20ms threshold required for a great VR experience. Keeping latency low between a user’s head movement and the corresponding movement on the headset’s display is absolutely critical.

google-cardboard
See Also: The Past, Present and Future of Google and VR

One of the biggest reasons why Samsung’s Gear VR provides a much better Android-based VR experience than even Google’s current Android-based Cardboard VR offering is that Samsung and Oculus have created custom Android firmware for Gear VR-compatible Samsung phones which is specifically tuned for virtual reality. This custom firmware allows Gear VR to cut through Android’s inherent latency in several important technical ways, such as Asynchronous Time Warp rendering.

Today, standard builds of Android lack such VR-specific features, but the next version (Android N) is likely to be the first that’s tuned for VR performance. References to a ‘virtual reality mode’ have already been spotted in early builds of the new software, and we’re expecting to hear much more about about Android N’s VR-specific features at I/O 2016. Ultimately, we expect that Android N will bring the default Android software stack up to par with where Gear VR is today (hardware withstanding).

Android VR as an Ecosystem

cardboard

Mentions of an ‘Android VR’ plugin in Unreal Engine development documentation surfaced recently, raising questions about whether or not it has anything to do with Google’s VR initiatives.

SEE ALSO
Varjo's Enterprise Cloud XR Streaming Platform Now Supports Quest 3 and Quest Pro

I believe the answer is yes, but I’m putting my money on the term simply being the next step after Google’s Cardboard initiative (rather than referencing an individual headset/product).

As it stands now, Cardboard is precisely that: an ecosystem descriptor. It describes a class of ‘dumb’ VR viewers (which do nothing more than hold your smartphone in front of some lenses), and the software ecosystem that goes with them (both the tools and the apps that are made for Cardboard).

Android VR as a term is likely to encompass both the new VR-specific software features of Android N along with a new class of VR viewer headsets and apps which go beyond Cardboard’s current capabilities.

No All-in-one Headset

google-cardboard-design-lab-app

While some have speculated that the rumored ‘Android VR’ is an all-in-one headset being developed by Google, I don’t see Google taking such an approach (at least not at I/O 2016). It simply doesn’t make sense from a strategic standpoint.

As the facilitator of Android, Google’s goal is to help its hardware partners sell phones. Android’s biggest competitor is iOS and Apple; the end goal of anything Google does with Android is to increase Android’s marketshare over iOS, not to steal marketshare from its hardware partners that fuel the successful Android ecosystem.

Creating an open ecosystem of smartphone-based peripheral headsets (as they’ve done with Cardboard) is the exact same successful strategy Google used for smartphones: supply the software (and occasionally, hardware reference designs) and let hardware partners furnish the hardware side with many competing choices for customers. Opening the door to allow any of their partners to create smartphone-based Android VR headsets (rather than Google creating their own an all-in-one) encourages the key objective of selling more Android phones across the ecosystem.

SEE ALSO
'Bulletstorm VR' Review – An Uglier & More Tedious Version of the Game You Love

Look at it this way: if Android has great VR and iOS has no VR, it’s going to be a huge opportunity for Google to lure iOS users to Android (such opportunities don’t come around that often, so Google is going to want to push this hard). Selling an all-in-one headset wouldn’t encourage an Apple customer to join the Android smartphone ecosystem (because they could then get the Android VR experience without converting to an Android smartphone). Making the smartphone the key to Android’s VR experience gives customers a major reason to switch to an Android smartphone and serves Google’s key objective of helping hardware partners to sell phones (and soon, headsets).

Continue Reading: Android VR Headsets Bring Straps and On-board HardwareCardboard Lives On (for Now)

1
2
Newsletter graphic

This article may contain affiliate links. If you click an affiliate link and buy a product we may receive a small commission which helps support the publication. More information.


Ben is the world's most senior professional analyst solely dedicated to the XR industry, having founded Road to VR in 2011—a year before the Oculus Kickstarter sparked a resurgence that led to the modern XR landscape. He has authored more than 3,000 articles chronicling the evolution of the XR industry over more than a decade. With that unique perspective, Ben has been consistently recognized as one of the most influential voices in XR, giving keynotes and joining panel and podcast discussions at key industry events. He is a self-described "journalist and analyst, not evangelist."
  • Zach Mauch

    For your argument against Google creating a stand alone headset, you are failing to consider the nexus hardware. The true purpose of nexus phones is having both development hardware for programmers and reference hardware for manufactures. For Android VR, these are still very valid needs.

    I don’t doubt that google may focus on the phone based VR headsets, but if they intend for Android VR to be used with stand alone headsets a “nexus” reference headset is needed.

    • benz145

      Whether or not they make an all-in-one is independent of whether or not they make a Nexus-branded device. I noted that they make reference hardware in the article and don’t rule that out, my main point about no all-in-one is that users are already buying 90% of the guts needed for a VR headset (their smartphones), why ask them to pay an additional 100% for an all-in-one instead of just adding the extra 10% needed to the phones they are already buying. Indeed, that’s the direction they announced at I/O.