Replit Adds Support for Meta Ray-Ban Display and Quest Apps
ReplitReplit added Agent instructions and QR-code preview tooling for building apps that target Meta Ray-Ban Display glasses and Meta Quest devices, timed to Meta's decision to open both platforms to third-party web and mobile developers. Developers can now prompt Agent with device-specific context so it produces apps that account for the glasses' small heads-up display, wrist-based Neural Band input, and voice controls, then preview builds directly on-device via QR code. The move positions Replit as a fast on-ramp for the newly opened Meta wearables developer ecosystem, without requiring a new language, SDK, or framework.
Key Takeaways
- Replit now supports building for Meta Ray-Ban Display glasses and Meta Quest devices, arriving alongside Meta's decision to open both platforms to outside developers.
- Agent instructions account for the glasses' constrained heads-up display and alternative input methods like voice, dictation, and Neural Band wrist gestures.
- A new QR-code preview flow lets developers load in-progress builds directly onto physical Ray-Ban Display or Quest hardware for testing.
- The feature requires no new programming language, SDK, or framework, reusing developers' existing web app skills.
- The launch times directly to Meta Connect 2026, where Meta first opened its wearables to third-party app developers.
- The move gives Replit users an early foothold in wearable computing, a device category most web developers have not previously built for.
Building for Meta's Wearables, Directly From Replit
Following Meta's decision at Meta Connect 2026 to open Ray-Ban Display glasses and Quest devices to third-party developers for the first time, Replit added dedicated support for building apps that target those devices. The feature ships as a mix of Agent instructions and an on-device QR-code preview flow rather than a separate product, so it fits directly into Replit's existing workspace.
Device-Aware Agent Instructions
Ray-Ban Display glasses present a much smaller heads-up display than a phone or laptop screen, and input happens through voice, dictation, on-screen keyboard, or wrist gestures captured by Meta's Neural Band, rather than a mouse and keyboard. Replit's new Meta device instructions give Agent that context up front, so generated apps account for the constrained display and non-traditional input methods instead of assuming a standard web layout. Developers building for Meta Quest headsets get a similar treatment tuned to that device's larger, immersive display instead.
QR-Code Preview on Real Hardware
Rather than relying on a simulator, the new workflow lets developers scan a QR code to load their in-progress build directly onto a physical Ray-Ban Display or Quest device for testing. That shortens the loop between describing a change to Agent and seeing exactly how it behaves on the glasses' small display or the headset's field of view.
Why It Matters
Meta only recently opened the door for outside developers to build for its wearables at all, offering both a mobile-app path and a web-app path without requiring a new programming language or framework. By wiring up Agent instructions and preview tooling for that specific developer preview on day one, Replit gives its existing user base a fast route into an entirely new device category, wearable computing, using the same conversational workflow they already use to build web apps.