Every Frame Perfect

Overall reaction to the article

• Many readers strongly resonated with the frustration over janky UI animations and “glitchy” feel across modern software.
• Others felt the piece described problems well but lacked constructive guidance or positive examples, leaving them unsure what “good” should look like.
• Some considered the critique overblown or too idealistic without acknowledging implementation difficulty or trade‑offs.

Value of animations vs instant transitions

• One camp argues most UI animation is unnecessary or harmful:
  • Adds latency and makes systems feel slow.
  • Distracts attention, especially when motion happens outside the focal area.
  • Many users report turning off animations (Android, GNOME, etc.) and finding the experience faster and clearer.
• Another camp argues motion is critical in some contexts:
  • Helps reorient users when layouts change or complex views transition.
  • Can reduce cognitive load when used briefly, non‑blocking, and under ~100–150 ms.
  • Games and certain tools demonstrate effective, purposeful animation.

"Every frame perfect" principle

• Supporters: intermediate frames that are logically inconsistent, overlapping, or “teleporting” undermine clarity and trust; if a midpoint screenshot looks nonsensical, the motion is probably wrong.
• Critics:
  • Human perception is about continuous motion, not still frames; frame‑by‑frame coherence is a poor yardstick.
  • Compare to film/cartoon smear frames and motion blur: bad as stills, effective in motion.
  • The article is seen as setting an unworkable or ill‑defined maxim without showing alternate designs.

Apple / modern UI quality

• Many comments lament a decline from earlier macOS/iOS eras, citing:
  • Chaotic Safari search bar, save dialog, sidebars, Preview zoom, Safari tab behavior.
  • SwiftUI / modern animation stack as more powerful but easier to misuse, leading to compositional glitches.
• Some note that earlier Apple UIs felt more polished; now animations often feel like hacks or regressions.

Latency, responsiveness, and user control

• Strong consensus that low latency is paramount.
• Animations should never:
  • Block input.
  • Introduce extra waiting beyond actual work being done.
• Short, cancellable, meaningful transitions are widely accepted; decorative or slow ones are heavily criticized.

Missing solutions and practical constraints

• Multiple readers wanted concrete “before/after” examples, design recipes, or implementation techniques.
• Others point out real‑world constraints: layout engines, cross‑framework animation systems, performance budgets, and business priorities often make “every frame perfect” unrealistic outside niche or high‑budget products.