Why two runners?
MediaPipe Holistic gives a mature baseline with dense face, hand, and body landmarks. The custom path keeps the interface honest by showing what a smaller whole-body model can do when it is quantized for a browser runtime.
whole-body pose toolkit
The custom-model story
Pose Tracker compares a production MediaPipe runner with a compact RTMPose-style model path in the same browser viewport. The point is to make the tradeoffs visible: latency, landmark density, device support, and how much motion detail survives when everything stays local.
What stays private?
Camera frames are processed in the page. No video leaves the device; the network is used only to load the app shell and model assets.
What is being measured?
The HUD focuses on frame rate, runner choice, smoothing behavior, and visual stability. Those are the parts a real interactive pose tool lives or dies on.