Skip to content

Get Started

The Cognitive3D SDK for Meta Spatial SDK adds analytics to native Android apps built with Meta's Spatial SDK for Meta Quest headsets. It records where participants look, how they move, and how they use your app, so you can see which content holds attention and where people struggle.

The Meta Spatial SDK and Android XR versions share the same Cognitive3DManager API. Custom events, sensors, and session properties work the same way on both platforms. Installation, permissions, and the entity type you pass to Dynamic Objects differ.

Supported devices

The SDK runs on Meta Quest headsets supported by the Meta Spatial SDK, including Meta Quest 3, Meta Quest 3S, and Meta Quest Pro.

Prerequisites

  • An Android app built with the Meta Spatial SDK 0.10.1 or later.
  • A main activity that extends AppSystemActivity, or another VrActivity subclass.
  • Minimum SDK: 29.
  • Kotlin 1.9+ or Java 11+.
  • A Cognitive3D account and application API key. Sign up for free.

What the SDK records automatically

Once installed, the SDK records the following without any additional code:

  • Head position and head-based gaze.
  • Controller and hand positions, including which input type is active.
  • Frame rate as a default sensor.
  • Device, OS, and app details as session properties.

Note

On Meta Spatial SDK, gaze is based on head direction. Eye tracking isn't used, including on Meta Quest Pro.

Example use case: collaborative workspace

The guides in this section use the same collaborative workspace app as the Android XR guides: an app where distributed teams load 3D models, move them in shared space, and annotate them with spatial markers.

In this guide

intercom If you have a question or any feedback about our documentation please use the Intercom button (purple circle) in the lower right corner of any web page or join our Discord.