PoseTracker integration

Choose the best integration option (camera, uploaded files, deprecated pixel tracking).

Pick the integration that matches your product constraints.

Solution 1: Real-time camera / webcam (recommended)

Use a hosted Tracking page in a WebView or iframe.

It handles:

• camera permissions

• real-time pose estimation

• overlay rendering (skeleton)

• exercise tracking (posture + counter + optional dev features)

When to use:

• you need live guidance

• you want the simplest integration path

• you want the best UX on mobile (camera permissions handled once)

Start here:

• Quick start (camera / webcam)

Solution 2: Upload Tracking (video & image)

Use a hosted page that lets the user upload a file (or you pass a remote URL).

Principle:

• You embed upload_tracking in a WebView.

• The page loads a video or image.

• Pose estimation runs in the browser.

• Results are sent back to your app via WebView messages.

What it’s great for:

• analyze existing media (camera not required)

• remove camera permission complexity

• process a single image (one-shot) or a full video

Start here:

• Upload Tracking endpoint (video & image)

• Shared params with the camera endpoint: Shared query parameters (Tracking + Upload Tracking)

Solution 3: Pixel tracking (⚠️ Deprecated ⚠️)

Pixel tracking is deprecated.

Keep it only for legacy integrations.

Docs:

• Pixel tracking (⚠️ Deprecated ⚠️)