Horizon Platform SDK on Meta Spatial Simulator - Overview

Updated: Jan 8, 2026

Horizon Platform SDK is offered in a set of Kotlin packages you can integrate in your Android app. Each of these features can be used independently, but using multiple in combination provides more engaging VR experiences.

Horizon Platform SDK is supported on Meta Spatial Simulator as a sandbox for testing Platform SDK APIs. The APIs use a test environment to interact with a local database using mocked data. For more information about how the test environment functions, see Spatial Simulator test environment.

Additional interactions to the environment are available via a command-line interface (CLI). For more information about the CLI, see Spatial Simulator CLI.

Supported features

All Platform SDK APIs available via the Kotlin Horizon Platform SDKs are supported in Spatial Simulator. The APIs on Spatial Simulator may differ from the headset version in the ways described below.

Push Notification

API	Behavior in Spatial Simulator
`PushNotification.register`	Does not register a real notification.
`PushNotification.unregister`	No effect.

Group Presence

Use Group Presence to add multiplayer features and presence to your Android apps.

API	Behavior in Spatial Simulator
`GroupPresence.launchInvitePanel`	Opens a system dialog that simulates the headset experience.
`GroupPresence.launchRosterPanel`	Opens a system dialog that simulates the headset experience.
`GroupPresence.getInvitableUsers`	Returns all users who are friends of the logged in user and filters out any users who have been blocked. From the spatial simulator default catalog, these users should initially include all users besides Lancelot and Thorne.
`GroupPresence.set`
`GroupPresence.setIsJoinable`
`GroupPresence.setDestination`
`GroupPresence.setLobbySession`
`GroupPresence.setMatchSession`
`GroupPresence.setDeeplinkMessageOverride`
`GroupPresence.getSentInvites`	By default, this API will return no results. By calling `sendInvites`, invites will be tracked and returned.
`GroupPresence.sendInvites`	Send an invite to the recipient ID, which can be accepted via CLI command.
`GroupPresence.clear`
`GroupPresence.joinIntentReceived`	This is a notification based API that can be triggered through the CLI command. Begin by listening for the notification by calling the joinIntentReceived API.

IAP (In-App Purchases)

API	Behavior in Spatial Simulator
`Iap.getProductsBySku`	Returns products from the default catalog which have matching SKU names as the names passed in. Create more SKUs by using the CLI command `iap.create_product`.
`Iap.launchCheckoutFlow`	Opens a system dialog that simulates the checkout dialog on the headset. Completing the checkout flow purchases the item.
`Iap.getViewerPurchases`
`Iap.getViewerPurchasesDurableCache`	Returns same set of purchases as `getViewerPurchases`
`Iap.consumePurchase`	Consumes a consumable type purchase. Must be a valid purchase which can be obtained from `Iap.getViewerPurchases`.

Users

API	Behavior in Spatial Simulator
`Users.get`
`Users.getAccessToken`	Returns a fake access token.
`Users.getLoggedInUserManagedInfo`
`Users.getLoggedInUserFriends`
`Users.getUserProof`
`Users.getOrgScopedId`
`Users.getSdkAccounts`
`Users.getBlockedUsers`

Application

API	Behavior in Spatial Simulator
`Application.launchOtherApp`	Opens a dialog. Unlike the headset, the Spatial Simulator does not launch a different application in the user’s library.
`Application.getVersion`	Returns the same information regardless of the calling application.

Application Lifecycle

API	Behavior in Spatial Simulator
`ApplicationLifecycle.launchIntentChanged`	This is a notification based API that can be triggered through the CLI command. Begin by listening for the notification by calling the `launchIntentChanged` API.
`ApplicationLifecycle.getLaunchDetails`	Returns “NORMAL” launch.
`ApplicationLifecycle.logDeeplinkResult`	Returns a hard-coded response with sample deeplink data.

User Age Category

API	Behavior in Spatial Simulator
`UserAgeCategory.get`	Returns the adult “AD” age category.

Known limitations

Other known limitations of the Horizon Platform SDK integration on Spatial Simulator include:

The currently logged in user cannot be changed.

The database cannot be cleared entirely. It can only be reset to its default state using CLI commands.

UI dialogs are simplified simulations of the actual headset experience.

No network requests are made - all data is local and simulated.

Did you find this page helpful?