Adaptive quality

​

capturePriority

<PoseTrackerProvider options={{ capturePriority: 'performance' }} />
// or
<PoseTrackerProvider options={{ capturePriority: 'quality' }} />

​

qualityChoice

<PoseTrackerProvider
  options={{
    qualityChoice: 'AdaptiveChoice', // default
    // or pin: 'prime' | 'pro' | 'lite' | 'ultralite' | 'basic'
  }}
/>

​

Profiles

​

FPS floors

1. Warm-up estimate — zeros bench before getUserMedia; may pick a lower profile (warmup_estimate).
2. Live auto-downgrade — median inference ms stays too high → drop one tier (low_fps), emit quality_changed.
3. performance_warning — still below floor on basic → device_too_slow (throttled).

​

Crash-loop guard

​

Host listeners

usePoseTracker({
  onQualityChanged: (e) => {
    // e.previousProfile, e.activeProfile, e.reason, e.detail
  },
  onPerformanceWarning: (e) => {
    // e.code === 'device_too_slow', e.meanFps, e.message (English)
  },
});

const { quality } = usePoseTracker();
// quality.activeProfile, meanFps, minTargetFps, idealFpsRange, capturePriority, …

​

Recommendations

1. Keep qualityChoice: 'AdaptiveChoice' and capturePriority: 'performance'.
2. Handle onPerformanceWarning in your own UX / analytics (localize before end users).
3. Do not force prime on mid-range Android in production.
4. Install AsyncStorage so the crash-guard persists.

​

Related

• Events — quality_changed, performance_warning
• Provider options