VR Media Discovery: Reactions, Comments, and Bookmarks

Written by the Fulldive product engineering team, based on direct inspection of the repositories listed below.

VR media discovery is the part of mobile virtual reality entertainment that most specs do not describe. It is what happens after the rendering pipeline works: users need to find something to watch, remember it next time, and say something about it. Fulldive VR (package in.fulldive.shell, repository fulldiveVR/fulldive-unity) built reactions, comments, and bookmarks into its Android VR app during the 2020 release cycle, and the repository history shows how the social layer was stitched onto the video player.

Two commits in particular show the shape of the work:

Video reactions API wiring: commit e53affb9. This is the back-end handshake that lets the VR client tell a server the user reacted to a given video, and retrieve aggregate reactions to show back in the scene.
Comment-video exception fix: commit 5ad7a1fc. This is the less glamorous companion commit. A robust comment UI is not the feature that sells a headset app; a crash-free comment UI is the feature that keeps people using it.

Both commits land inside the era covered by the Fulldive VR release branches release_vr_5-13 and release_vr-x_5-10, which is where the ongoing VR entertainment app stabilized during 2020. Those branch names are the clearest repo-side evidence that Fulldive VR was being shipped as a regular release product, not as a demo — multi-release branches only make sense when there is an established release cadence.

Why bookmarks matter more than they sound

A bookmark in a phone-browser app is a list entry. A bookmark in a mobile VR app is the difference between “I can find the thing I want to watch” and “I need to take the headset off and search again.” Every tap and gaze action costs more in VR than it does on a 2D screen, because the user’s input surface is limited to controller buttons, gaze timers, or a virtual keyboard on a curved panel.

Bookmarks inside the Fulldive VR shell interact with the browser and video player pipeline we described in the 360 and 3D video post, including in-browser playback controls (commit f04087ba) and Cinerama flat-video rendering (commit 7a7f56f9). A saved item has to remember the URL, the player mode (Cinerama, 360, stereoscopic), and enough metadata to show a tile without re-fetching a page. That is a small feature to describe and a non-trivial feature to implement in a Unity VR scene.

Reactions and comments on a curved surface

The social UI has to render somewhere. In a Fulldive-style VR browser, the somewhere is usually a curved panel attached to the video surface or the headset view. Reactions are a good fit: small, tappable, visually obvious from any angle. Comments are harder. Long text on a curved surface requires careful font sizing, line-length limits, and a scroll interaction that works with controller input rather than touch.

The comment-video exception fix (5ad7a1fc) is the kind of commit that shows up when a comment screen tries to open before the video metadata has arrived, or when a video has been removed from the back-end since the last cache was built. Both situations are routine in a social media app; inside VR, an unhandled exception is especially disruptive because the user cannot alt-tab out.

Release branches as product evidence

Release-train branches are underrated as repo evidence. release_vr_5-13 and release_vr-x_5-10 imply:

Multiple concurrent release lines (the -x suffix) for different build targets.
Versioning granular enough to keep minor releases stable while feature work continues.
A cadence that matches a real store-facing product, not an internal prototype.

Combined with the social layer commits, this is how Fulldive VR qualifies as mobile virtual reality entertainment rather than a tech demo. It had users; users could react to videos; users’ reactions aggregated; comment fetching had to be defensive against backend state.

What this does not do

Some boundaries worth stating: the reactions and comments system described here is historical repository evidence for the 2020 Fulldive VR release cycle. We are not claiming current parity with any specific social platform; we are not promising that comments on any given third-party video provider are routed into Fulldive VR today; and Fulldive VR has never claimed to be a content network in its own right. Users who are comparing VR media discovery apps should check current store listings and try the app directly before relying on any specific social feature.

How Fulldive VR plays 360 and 3D video on Android explains the player layer under the social features.
Why mobile VR apps need headset-specific work describes why features like comment panels have to be re-tested per SDK.
Rebuilding Fulldive VR: Unity migration and legacy repairs covers the feed and build history that shaped the 2020 releases.
What a mobile VR app can and cannot do in 2026 frames the state today.
The Fulldive company story shows how VR discovery features informed later products like WizeUp.

Sources

Repository evidence: fulldiveVR/fulldive-unity, commits e53affb9, 5ad7a1fc, f04087ba, 7a7f56f9, and release branches release_vr_5-13 and release_vr-x_5-10; history inspected 2026-04-13.
External reference: Google VR Video360 Android sample for how mobile VR projects handle video surfaces.
External reference: Android Developers — XR overview for platform context.

Last updated: 2026-04-16. Commit hashes and version numbers are drawn from Fulldive repositories inspected on 2026-04-13.