to-spring-or-not-to-spring

Audit animation code to identify and report misapplied timing functions, outputting file:line findings for quick fixes. It evaluates velocity preservation and parameter balance to enforce proper spring and easing usage.

Analyze animation code to enforce practical rules for velocity preservation and balanced parameters, generating file:line findings. This helps debug UI transitions that feel physically inaccurate during interruptions.

Run an animation timing analyzer on your codebase to evaluate interaction types and generate file:line findings. It detects proper timing function usage based on whether interactions involve gestures or system-driven changes.

Yes, the analyzer applies to UI interactions, transitions, and motion libraries where velocity and interruption matter. It evaluates rule-based timing function selection for gestures and state changes.

Easing functions are limited because they do not preserve velocity or handle interruptions gracefully during gestures. Using easing for interactive motion results in animations that feel rigid and physically inaccurate when interrupted.