2D Android companion app development

Updated: May 12, 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
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)

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.

SDK for companion apps

To build a 2D Android companion app that integrates with Meta Quest platform services, use the Horizon Platform SDK for Android. This SDK provides access to platform features from a standard Android app, including:

Authentication: Use Meta account authentication to identify users across your Quest VR app and mobile companion app. See Authentication for implementation details.

Platform services: Access leaderboards, achievements, and other platform features 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.

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.