> For the complete documentation index, see [llms.txt](https://multiset.gitbook.io/multiset/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://multiset.gitbook.io/multiset/native-support/android-native/sample-activities.md).

# Sample Activities

This section provides detailed documentation for the sample activities included in the MultiSet Android SDK. These activities demonstrate how to implement VPS localization and object tracking in your Android application.

## Available Activities

### [MainActivity](/multiset/native-support/android-native/sample-activities/mainactivity.md)

The entry point for the SDK demo application. Handles SDK initialization, authentication, and navigation to both the AR localization and object tracking activities. Displays a card-based UI with a Localization card (mode picker + Start button) and an Object Tracking card.

### [MultiSetLocalizationActivity](/multiset/native-support/android-native/sample-activities/multisetlocalizationactivity.md)

Unified AR localization activity that supports both single-frame and multi-frame localization modes. The mode is selected at launch time via an intent extra.

### [ObjectTrackingActivity](/multiset/native-support/android-native/sample-activities/objecttrackingactivity.md)

Dedicated AR activity for detecting and tracking pre-registered physical objects. Once an object is tracked, its 3D mesh is fetched from the MultiSet platform and rendered in the AR scene with an animated glowing outline shader.

***

## Localization Mode Comparison

| Feature         | Single-Frame       | Multi-Frame         |
| --------------- | ------------------ | ------------------- |
| Frames captured | 1                  | 4–6 (configurable)  |
| Accuracy        | Good               | Better              |
| Capture time    | Instant            | \~2–3 seconds       |
| Network usage   | Lower              | Higher              |
| Best for        | Quick localization | Precise positioning |

***

## Object Tracking at a Glance

| Feature              | Description                                             |
| -------------------- | ------------------------------------------------------- |
| Supported objects    | Up to 10 simultaneously                                 |
| Mesh rendering       | GLB fetched from platform, outline-only animated shader |
| Auto-tracking        | Starts automatically on session ready                   |
| Background tracking  | Periodic re-tracking after first success                |
| Confidence filtering | Rejects low-confidence results automatically            |

***

## Getting Started

1. Initialize the SDK and authenticate in `MainActivity`
2. **For localization:** configure `LocalizationConfig`, then launch `MultiSetLocalizationActivity`
3. **For object tracking:** configure `ObjectTrackingConfig`, then launch `ObjectTrackingActivity`

See [LocalizationConfig](/multiset/native-support/android-native/api-reference/localizationconfig.md) and [ObjectTrackingConfig](/multiset/native-support/android-native/api-reference/objecttrackingconfig.md) for full configuration options.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://multiset.gitbook.io/multiset/native-support/android-native/sample-activities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.