RaceEye

Since you're building a RaceEye project—likely a performance tracker, a spectator tool, or a driver-assistance interface for racing (potentially using that PICO OS 6 Web App tech we discussed)—here is a high-energy, professional structure to fill those sections.

Inspiration

The thrill of racing is often lost in a sea of complex telemetry and tiny data screens. We wanted to bridge the gap between the raw speed of the track and the digital data that defines modern racing. Inspired by high-end Formula 1 steering wheel displays and the immersion of VR, we set out to create RaceEye: a spatial computing dashboard that lets drivers or fans see exactly what matters, when it matters, without the clutter of a traditional browser.

What it does

RaceEye is a PWA-driven spatial application designed for PICO OS 6. It transforms real-time racing telemetry into a "Shared Space" experience. Users can:

Launch Standalone: Transition from a web link to a dedicated, borderless VR window instantly.

Multi-Window Telemetry: Open separate spatial windows for lap times, tire temperatures, and track maps.

Adaptive UI: Automatically switches navigation modes based on whether it is running in the PICO Browser or as a Standalone App.

Immersive Overlays: Uses the WebSpatial API to create transparent, floating HUDs that integrate directly into the user's environment.

How we built it

We leveraged the power of modern Web APIs and the PICO Web Runtime.

Frontend: Built with a responsive framework and optimized with CSS Media Queries for display-mode: standalone.

PWA Architecture: Developed a robust manifest.json with specific scoping to ensure the "Open as Standalone" trigger is seamless in PICO OS 6.

Logic: Utilized window.matchMedia to detect the Web Runtime and dynamically toggle between minimal-ui (system navigation) and standalone (custom in-app navigation).

Spatial Integration: Implemented the WebSpatial API to manage window transparency and multi-window positioning in the PICO Shared Space.

Challenges we ran into

The biggest hurdle was mastering the transition between the PICO Browser and the Standalone App mode. We had to ensure that our session data persisted when the user clicked the "Open as standalone app" button. Additionally, designing a UI that works both as a flat 2D webpage and a floating VR container required several iterations of our spatial CSS layout to avoid "clipping" in the VR environment.

Accomplishments that we're proud of

We are incredibly proud of achieving a zero-native-UI look. By successfully implementing the standalone display mode, we stripped away the browser's address and tab bars, making RaceEye feel like a native VR application built entirely with web technologies. We also successfully implemented a multi-window system where each telemetry module acts as its own Spatial Container.

What we learned

We learned the deep intricacies of the PICO OS 6 Web Runtime and how PWA standards are being adapted for spatial computing. We gained a new appreciation for the display-mode media query and how it can be used to provide a tailored user experience across different "runtimes" without writing separate codebases.

What's next for RaceEye

The next lap for RaceEye involves integrating WebXR for even deeper immersion, allowing users to "place" telemetry data directly onto a 3D track model. We also plan to optimize our data pipeline to handle higher-frequency telemetry from professional simulators like iRacing and Assetto Corsa, making RaceEye the ultimate companion for every digital racer.

Built With

• openapi
• react