Later implementation is directed to run infinite-loop animations on active components
Source references: 5The specification explicitly tells a coding agent to implement infinite-loop states for every active dashboard component and cascaded delays for lists.
With many active components, continuous animation can increase CPU/GPU use and battery consumption and may cause discomfort for motion-sensitive users. The supplied material gives no stopping condition.
The document says these animations are not run by Stitch itself but are implementation instructions for a later coding agent. It requires an infinite loop on every active dashboard component and delayed cascades for lists and grids. This can create continuing CPU/battery use and distraction, with no stated accommodation for reduced-motion preferences. Isolating CPU-heavy animations and targeting 60fps are mitigation guidance, not elimination of the risk. Users can require finite-by-default motion, pause controls, and reduced-motion support.
## 8. Motion & Interaction (Code-Phase Intent)> **Note:** Stitch generates static screens — it does not animate. This section documents the **intended motion behavior** so that the coding agent (Antigravity, Cursor, etc.) knows exactly how to implement animations when building the exported design into a live product.- **Physics Engine:** Spring-based exclusively. `stiffness: 100, damping: 20`. No linear easing anywhere. Premium, weighty feel on all interactive elements- **Perpetual Micro-Loops:** Every active dashboard component has an infinite-loop state — Pulse on status dots, Typewriter on search bars, Float on feature icons, Shimmer on loading states- **Staggered Orchestration:** Lists and grids mount with cascaded delays (`animation-delay: calc(var(--index) * 100ms)`). Waterfall reveals, never instant mount- **Layout Transitions:** Smooth re-ordering via shared element IDs. Items swap positions with physics, simulating real-time intelligenceShow 4 other places
- **Spring Physics default:** `stiffness: 100, damping: 20` — premium, weighty feel. No linear easing- **Perpetual Micro-Interactions:** Every active component should have an infinite loop state (Pulse, Typewriter, Float, Shimmer)- **Staggered Orchestration:** Never mount lists instantly — use cascade delays for waterfall reveals- **Performance:** Animate exclusively via `transform` and `opacity`. Never animate `top`, `left`, `width`, `height`. Grain/noise filters on fixed pseudo-elements only- **Physics Engine:** Spring-based exclusively. `stiffness: 100, damping: 20`. No linear easing anywhere. Premium, weighty feel on all interactive elements- **Perpetual Micro-Loops:** Every active dashboard component has an infinite-loop state — Pulse on status dots, Typewriter on search bars, Float on feature icons, Shimmer on loading states- **Staggered Orchestration:** Lists and grids mount with cascaded delays (`animation-delay: calc(var(--index) * 100ms)`). Waterfall reveals, never instant mount- **Perpetual Micro-Loops:** Every active dashboard component has an infinite-loop state — Pulse on status dots, Typewriter on search bars, Float on feature icons, Shimmer on loading states- **Staggered Orchestration:** Lists and grids mount with cascaded delays (`animation-delay: calc(var(--index) * 100ms)`). Waterfall reveals, never instant mount- **Layout Transitions:** Smooth re-ordering via shared element IDs. Items swap positions with physics, simulating real-time intelligence- **Hardware Rules:** Animate ONLY `transform` and `opacity`. Never `top`, `left`, `width`, `height`. Grain/noise filters on fixed, pointer-events-none pseudo-elements only- **Performance:** CPU-heavy perpetual animations isolated in microscopic leaf components. Never trigger parent re-renders. Target 60fps minimum