Every Frame Perfect
Points and comments are a snapshot, not live.
UI animations must remain coherent in every frame to build user trust and convey polish.
The article applies Wayland's principle of "every frame is perfect" to user interface design. The core rule: if a screenshot is taken at any moment during an interaction, the UI must make sense. Specific failures include white flashes between screens, partially loaded content, relayout during loading, internal inconsistency (one UI element saying "1 update available" while another says "Checking for updates"), and imprecise animations. The author provides video examples from Safari, Photos, YouTube, and Preview showing animations where elements desynchronize (placeholder text and cursor moving from different positions), where content snaps while borders animate, or where transitions create false impressions of state changes. These problems stem from treating animation as an afterthought rather than designing it alongside start and end states.
What commenters are saying
Commenters largely agree the article identifies real problems affecting most software, though several note the lack of positive examples showing corrected versions. A secondary debate emerges: whether animations are necessary at all. Some argue motion aids reorientation after transitions and helps users follow state changes; others counter that instant transitions become imperceptible with use and that animations waste time for power users. One commenter linked their own detailed walkthrough of animation improvements. The thread reflects tension between software as tool (favoring instant, imperceptible UI) versus software as product (favoring motion for perceived polish and beginner guidance).
A top subthread emphasizes the distinction between unnecessary animations and purposeful micro-interactions (hover effects, confirmation feedback) that convey meaningful state information to all user levels.