Meta Quest Mobile Companion App Integration

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.

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

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

1. Analysis and architecture — study your product, select communication channels, design the scheme.
2. Quest module development — write an Android service (Kotlin) with WebSocket/BLE/Meta SDK.
3. Mobile client creation — iOS (Swift) and Android (Kotlin) apps with deep linking and UI.
4. 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.

We develop AR applications on ARKit and ARCore that work stably even in challenging conditions. Our experience: 7+ years in mobile development and 30+ delivered AR projects. Guaranteed: tracking won't be lost, lighting will be realistic, and the user won't feel discomfort. Certified Apple and Google developers.

Why does tracking get lost and how to fix it?

ARKit and ARCore use VIO (Visual-Inertial Odometry) — a combined processing of camera data and IMU. Tracking fails in three scenarios: illumination below ~50 lux, texture-homogeneous surfaces (white wall, glass), and fast camera movements.

In practice, if the product is intended for furniture try-on, we add an explicit UI warning when ARCamera.TrackingState.limited(.insufficientFeatures). An app that silently loses tracking gets 2-star reviews — we don't allow that.

Plane detection is configured via ARWorldTrackingConfiguration.planeDetection = [.horizontal, .vertical]. Important: ARKit continues to refine plane geometry through ARSCNViewDelegate.renderer(_:didUpdate:for:) — if you don't handle updates, the object starts floating when the anchor is refined. Our team solves this at the architecture stage, not during testing.

AR Foundation: cross-platform with nuances

Unity AR Foundation is an abstraction layer over ARKit and ARCore. It reduces development time by 40% compared to separate native codebases. But some features (e.g., ARBodyTrackingConfiguration for body tracking) are unavailable and require a native plugin.

For React Native and Flutter, direct AR Foundation is missing. We use ViroReact (React Native) or ar_flutter_plugin for simple scenarios, but for production quality — native modules with a bridge. Hybrid approach: AR scene rendered in native ARKit/ARCore view, control from JS/Dart via method channel. Included in our standard delivery.

Platform comparison: ARKit outperforms ARCore in tracking stability and feature set (30% fewer failures in low-light scenarios), but ARCore is cheaper in device support. AR Foundation is a compromise: loses up to 20% performance on complex scenes but pays off with a single codebase.

Try-on: product fitting via AR

Fitting glasses, jewelry, cosmetics — a separate class of tasks. Here, face tracking is needed, not plane detection.

ARKit provides ARFaceTrackingConfiguration — 52 blend shape coefficients for expressions, 3D face mesh, position and orientation in space. Works only on devices with TrueDepth camera (iPhone with Face ID).

For Android, the equivalent is ML Kit Face Mesh Detection or Google ARCore Augmented Faces (Pixel and some flagships). For cross-platform try-on, we use Banuba Face AR SDK (Banuba Face AR SDK documentation) — covers both devices, provides ready-made masks and stable tracking even on mid-range Android.

Try-on quality critically depends on 3D product models. Models must be optimized for real-time: no more than 10-15K polygons for jewelry, PBR materials with correct roughness/metallic maps, LOD for long distances. Within our engagement, we provide ready-made optimization guides.

How to achieve realistic lighting in AR?

ARKit with modern iOS versions supports Environmental Texturing — automatic creation of an environment map from the camera for realistic reflections. Enabled via ARWorldTrackingConfiguration.environmentTexturing = .automatic. Without it, metallic and glass materials look plastic.

ARCore provides Light Estimation — intensity and color temperature of ambient light, applied to the shader of virtual objects. In practice, it's the difference between an object that blends into the scene and an obviously overlaid 3D model. We guarantee that the final image doesn't betray virtuality.

What's included

• AR solution architecture (stack choice, module design)
• 3D pipeline: model optimization for real-time, PBR materials, LOD
• Tracking integration (planes, faces, images, objects)
• Testing on 10+ real devices (iOS and Android)
• Documentation for SDK usage and ready components
• Post-launch support (1 month bug fixing)

Timeline and estimation

Simple AR scene with placing one 3D model on a plane — 1-2 weeks. Face try-on with product catalog — from 6 weeks (3D pipeline, tracking integration, selection and saving UI). Full AR shopping with cloud anchors and multiplayer — from 3 months. We'll estimate your project in 1 day — contact us to discuss your AR idea.