Sometimes a user puts on a Meta Quest headset but wants to control content from their phone: pick a game, adjust privacy settings, transfer photos. For example, launching a game from the library without taking off the headset, or receiving an incoming message notification in VR. We develop mobile companion apps that connect the VR headset and smartphone through various channels—from the official Meta SDK to direct local network. The result is a seamless experience without switching the headset. Our team has 5+ years of experience and 30+ successful cases—from simple control to multi-user social VR platforms. Backend infrastructure savings can reach 40% when using direct channels.
How to organize communication between Quest and a mobile app?
Several technical channels exist. The choice depends on the scenario: media streaming, command control, multiplayer. Below is a comparison table.
| Method | Speed | Latency | Use Case | Complexity |
|---|---|---|---|---|
| Meta Platform SDK | – | – | Authorization, invites, pushes | Medium (OAuth, API) |
| Local network (LAN) | 100 Mbit/s+ | 5–10 ms | Control, telemetry | Low (WebSocket/HTTP) |
| Bluetooth | ~1 Mbit/s | 50–100 ms | Remote control, small data | Medium (GATT) |
| USB (ADB) | 480 Mbit/s | <1 ms | Development only | High (cable required) |
Meta Platform SDK — the official bridge between environments. It implements unified authorization (Meta Login, OAuth 2.0), notifications (friend online, room invitation), and deep linking (oculus://). If your product is social, this is a must have.
What does direct local network bring?
Quest 3 and phone on the same Wi-Fi — the most versatile channel. On Quest, an Android service with WebSocket runs; on the phone, an HTTP client. Discovery via mDNS (NsdManager on Android, Bonjour on iOS). This approach suits enterprise solutions where no public backend is needed—data never leaves the local network. This can save up to 40% on backend infrastructure development.
When is Bluetooth needed?
Only for low-speed commands: press a button, read telemetry. Bandwidth ~1 Mbit/s does not allow video, but no Wi-Fi is needed. Implemented via a GATT server on the Quest side.
Typical architecture
In a typical architecture, the mobile companion syncs with Quest through a cloud backend—this is more reliable than a direct channel. Diagram: [Phone] ←→ [Backend API] ←→ [Meta Quest]. For real-time interactions (phone as a controller) — WebSocket via relay server with 50–100 ms latency. If a social layer is required, we integrate Meta Multiplayer SDK (Photon + Meta Parties). The companion displays online friend statuses from Meta Social Graph (via Meta Login) and sends invitations to VR sessions. Time savings on social feature implementation — up to 50%.
Meta Platform SDK recommends using WebSocket for real-time communication between Quest and phone.
What the work includes
- Audit of the existing Quest app and selection of communication channels.
- Architecture design: server side (API, WebSocket), mobile clients (iOS/Android).
- Development of the companion module on the Quest side (Kotlin/Java).
- Integration with Meta Platform SDK: authorization, pushes, deep linking.
- Mobile app development for iOS (Swift) and Android (Kotlin) with Universal/App Links.
- Testing with a real Quest 3 (TestFlight/Google Play Console).
- Assistance with publishing in Meta Horizon Store (App Lab) and mobile OS stores.
- Technical support after launch.
Estimated timelines
| Integration level | Timeline |
|---|---|
| Basic LAN connectivity + content management | 6–10 weeks |
| Full Meta Platform SDK integration + social features | 3–5 months |
| Full cycle (analytics → UX → backend → mobiles → Quest) | from 4 months |
The exact cost is calculated individually after reviewing your project. Order companion app development, and we will implement the integration within the agreed timeline.
How we develop a companion app: 4 stages
- Analysis and architecture — study your product, select communication channels, design the scheme.
- Quest module development — write an Android service (Kotlin) with WebSocket/BLE/Meta SDK.
- Mobile client creation — iOS (Swift) and Android (Kotlin) apps with deep linking and UI.
- Testing and publishing — test on real device, deploy to App Store and Horizon Store.
Why order turnkey integration?
We are a team of mobile developers with 5+ years of experience in building VR companions. We have delivered over 30 projects for Meta Quest 2 and 3. We understand the nuances of App Store Review Guidelines (Section 4.2) and Meta Horizon Store requirements. We guarantee on-time delivery.
One common mistake is ignoring Section 4.2: a media player without its own content may be rejected. Another is mixing production and debug keys: the signature must match the Provisioning Profile in App Store Connect. Also, properly configure Background fetch so that friend status updates in the background don't drain the battery, and ProGuard/R8 for correct serialization.
Get a consultation — send your project description, and we will propose the optimal architecture and budget. Contact us for details.