Viscereality Companion

The broader Viscereality system includes a participant-facing Quest runtime, but researchers should not need to live inside that runtime project just to run a study. The companion app exists to translate Viscereality into a stable Windows operator surface: connect the headset, install the right build, check the live transport, and guide the session from one place.

That matters both for first-time collaborators and for labs that need a reproducible operator workflow. A good researcher-facing tool should reduce setup friction, narrow room for protocol mistakes, and make it obvious which parts of the session are healthy before a participant is already waiting.

The current public iteration is focused on getting the version for the collaboration with Hugo Critchley's lab at Sussex working cleanly end to end. That means the present release is not yet trying to be every possible multi-study operator surface. It is deliberately focused on a reliable install, launch, monitoring, and guided-session path for that collaboration first.

Once that path is stable, the same companion framework can be widened into a more general-purpose entry point for other Viscereality applications, other study shells, and other research or deployment contexts that need a clearer Windows-side control surface.

I am open for hire if a team needs specific adaptations to either the broader Viscereality app itself or the Windows companion. In practice that can mean narrowing the UI to a specific protocol, adding or simplifying telemetry, packaging a dedicated study surface, or aligning the operator workflow with the reality of a lab's setup rather than the assumptions of a generic tool.

The useful work here is usually translational: making a research system legible, reproducible, and operable by the people who actually need to use it.