How PODIE previews play without hiding the installation boundary
PODIE uses a different playback policy for browsing than an installed component may use in your application. The gallery demonstrates the effect; installation gives you source to integrate and control.
Load near the viewport and keep the preview
The gallery delays mounting new previews until they approach the visible area. Once a regular preview is loaded, it stays mounted when you scroll away, avoiding a repeated loading flash when you return. Animation activity is controlled separately from the lifetime of the preview.
The two full-site cards simulate different sequences of actions. They do not save those showcase actions into a visitor’s own projects. Their animation is a tour of local template behavior, not evidence of a running AI backend.
Why 3D waits for interaction
The 3D category starts on mouse hover or keyboard focus and stops when that interaction ends. Other categories play while visible. Category membership is the current policy: a WebGL implementation outside the 3D category does not automatically receive the same hover-only treatment.
On touch devices, open the detail page to interact with a 3D scene. Reduced-motion preferences can suppress gallery autoplay. A still preview should remain useful, and an essential action must never depend on noticing an animation.
What installation changes
The gallery controller is PODIE code. It is not automatically copied into every installed upstream component. An entrance effect may run once; a canvas may own a requestAnimationFrame loop; a self-contained scene may use its own scroll document. Read the selected component’s integration notes.
For your application, define when animation may run, stop work while it is offscreen, and supply a static alternative. Measure the complete page on target devices. We have not established a per-component mobile GPU score or a current field Core Web Vitals pass for the entire catalog.
Related reading and evidence
Last updated: .