Google announces new experimental Daydream VR features for developers: support for all Android apps, new 6DoF controllers, and a see-through mode
Jonathan Huang / Google Developers Blog :
Context & Ripple Effects
Daydream began in 2016 as a phone-locked play: a VR mode baked into Android N, a View headset and controller designed around comfort and simplicity, and VR SDK 1.0 graduating out of beta that September. In May 2017 Google widened the platform twice — first to untethered standalone headsets with positional tracking from Lenovo and HTC, then to a 2D function panel overlay with Chrome, screen capture, and Google Cast inside the headset.
Today's experimental release is the third step in that widening: instead of curating a VR-native catalog, Google is letting developers surface ordinary Android apps in Daydream, while 6DoF controllers and a see-through mode push the hardware beyond the original 3DoF design. The through-line is that Daydream stops being a walled VR storefront and starts behaving like a mode of Android itself.
First-order effects
- Developers no longer need to build VR-native apps to reach Daydream users — existing Android apps become the content library, directly extending the utility of the 2017 overlay work that put Chrome and screen capture inside the headset.
- Hardware partners Lenovo and HTC get a specification for next-generation standalone headsets built around 6DoF controllers rather than the simpler motion controller shipped with the original Daydream View.
Second-order effects
- Rival standalone VR platforms now compete against an entrant whose content problem is solved by inheritance — every Android app is potentially available — pressuring them to open their own catalogs or match the overlay-style 2D app access.
- See-through mode pulls Daydream toward mixed-reality use cases, forcing headset makers to weigh camera-equipped designs against the cost-optimized tethered-phone model the platform launched on.
Third-order effects
- If the pattern holds, mobile VR consolidates around the host operating system rather than dedicated app stores — the durable question being whether a platform that inherits its OS's entire app catalog outcompetes curated VR ecosystems.
- Blending 2D apps, 6DoF input, and passthrough vision points VR and AR hardware toward a single converged device category, with Google positioning Android as the software layer underneath both.
The trend: Mobile VR platforms are dissolving into their host operating systems, trading curated VR storefronts for inherited app catalogs and mixed-reality hardware.