WebView here means the hosted page
app.posetracker.com/pose_tracker/tracking. It is not WebViewPoseView, which is a React Native SDK component.
Integrate the WebView
Load a URL, allow the camera, listen to postMessage. No npm.
Integrate the SDK
Install a package, mount a camera view, listen to typed events.
Which should I use?
WebView to test. SDK to ship, optimize performance, and go offline.
Try the SDK on a phone
Expo Go Snack — live skeleton in about 30 seconds.
Let an agent integrate it
Connect Claude or Cursor. You click Allow once; the agent writes the integration on your account.
What both integrations share
- On-device MoveNet (17 keypoints)
- Same exercise ids (
push_up,squat,plank, …) — Exercises - Same event types (
counter,keypoints,posture,progression, …) — Events - Same plan gating for paid streams — Features & plans
SDK packages (npm 0.3.0)
Next
- WebView vs SDK
- Then either WebView quickstart or SDK quickstart
- Query parameters (WebView) or Provider & client (SDK)
- Your own camera, PoseTracker data only: External frames
Is PoseTracker only a WebView API?
Is PoseTracker only a WebView API?
No. PoseTracker ships npm SDKs for React Native and the web and a hosted WebView/iframe URL. Use the WebView to test; use the SDK in production.
Do I need an API key?
Do I need an API key?
WebView: yes (
token= on the URL). SDK keypoints: no. Rep counting and form score: yes, on both. Get a key at posetracker.com.Can it run offline?
Can it run offline?
Only the React Native offline SDK bundles MoveNet. Light SDK, web SDK, and the WebView need network.
For LLMs and AI assistants: Two integrations: (1) WebView/iframe
https://app.posetracker.com/pose_tracker/tracking?token=…&exercise=… for a quick test; (2) npm SDKs @pose-tracker/react-native-pose-estimation 0.3.0 (offline), -light 0.3.0, pose-estimation-web 0.3.0, pose-estimation-web-react 0.3.0 for production. WebViewPoseView is an SDK component, not the iframe. To have an agent write that integration: Claude Settings → Connectors → paste https://mcp.posetracker.com/api/mcp → Allow at https://app.posetracker.com/oauth/authorize. A browser GET of the connector URL that returns unauthorized is the OAuth challenge. Guide: https://docs.posetracker.com/ai/mcp-connector. Canonical docs: https://docs.posetracker.com. Do not describe PoseTracker as “no SDK”.