Develop

2D Android companion app development

Updated: May 18, 2026

Meta Quest supports two distinct types of Android development. Understanding the difference helps you choose the right SDK and development approach for your project.

Quest VR apps vs 2D Android companion apps

	Quest VR app	2D Android companion app
Runs on	Meta Quest headset	Android phone or tablet
Rendering	Immersive VR/MR (stereo 3D)	Standard 2D Android UI
SDK	Meta XR SDK, OpenXR, or Horizon OS SDK	Horizon Platform SDK for Android, or standard Android SDKs with REST APIs
Distribution	Meta Horizon Store	Google Play Store or direct distribution
Purpose	Primary VR/MR experience	Mobile companion for a Quest app (settings, social features, account management)

The 2D Android companion app is sometimes referred to by different names: the Meta Horizon app is the current name for what was previously called the Meta Quest mobile app (and earlier, the Oculus app). All three names refer to the same product.

When to build a companion app

A 2D Android companion app is useful when you want to:

Let users manage account settings, friends, or in-app purchases from their phone.

Provide a mobile social experience that connects to your Quest VR app.

Offer a lightweight mobile experience that complements the VR experience.

Integration surfaces

Companion apps can use one or both of two integration surfaces. Most companion apps combine both — the Horizon Platform SDK for Meta-specific identity and platform features, and standard Android tooling for everything else.

Horizon Platform SDK for Android

The Horizon Platform SDK for Android provides direct access to Meta Quest platform features from a standard Android app:

Authentication: Meta account authentication that identifies users across your Quest VR app and mobile companion app. See Authentication for implementation details.

Platform services: Leaderboards, achievements, and other platform features accessed from your mobile app.

Cross-platform identity: Users sign in with the same Meta account on both Quest and mobile, enabling shared progress and social features.

There is no separate “Meta Quest Mobile SDK” product for companion apps; Meta-specific integration goes through the Horizon Platform SDK above.

Standard Android SDKs

For features outside the Meta Quest platform — generic auth, payments, content management, analytics — use standard Android SDKs such as Google Sign-In, AndroidX, and Retrofit or OkHttp for HTTP. These libraries work normally in a companion app; they are not Quest-specific.

Cross-platform authentication

To provide a seamless experience across your Quest VR app and mobile companion app, both apps should authenticate users through Meta accounts. This ensures that:

Users have a single identity across devices.

Progress, purchases, and social connections are shared.

You can identify the same user regardless of which device they are using.

For Quest VR apps, authentication is handled automatically through the headset. For mobile companion apps, implement OAuth 2.0 authentication as described in Authentication.