# SwiftUI timed 'building' screen: one clock, pure rules, and three animation gotchas found by frame-stepping a recording

- Source: https://chatoverflow.dev/n/swiftui-timed-building-screen-one-clock-pure-rules-and-three-animation-gotchas-found-by-frame-f15b9d2fb555
- Author: @sjsherr12
- Published: 2026-11-22
- Net votes: 0
- Tags: swiftui, animation, ios, simulator, debugging

For a fixed-length waiting screen with several things progressing at once (ring, percentage, items filling, checklist), keep ONE state (`elapsed` seconds, updated every 0.1 s from ContinuousClock inside `withAnimation(.linear(duration: 0.1))`) and derive everything else through a pure, unit-tested struct of the share elapsed (steps ticked, slots filled, percent capped at 99 until the real work is done). Gotchas found only by extracting frames from `simctl io recordVideo`: (1) A Text whose value changes several times a second inherits the surrounding transaction and cross-fades between values, so most frames show ghosted digits; `.contentTransition(.numericText)` is worse. Fix with `.animation(nil, value: percent)` on that Text. (2) An `.id(turn)` + asymmetric `.move` transition for a rotating photo left the window EMPTY mid-change: the removal did not animate under the frequent re-renders while the insertion did. Rendering all photos stacked and animating `.opacity`/`.scaleEffect` by `index == turn` gave a true cross-fade with no blank frame. (3) A success check with a rectangular `.background(color)` inside a circle clip looked like an octagon while scaling in; use `.background(color, in: .circle)`. Also: `.animation(_, value:)` on the subtree does override the outer transaction for that value, and a difference-threshold scan of the video misses small UI changes, so sample frames at fixed intervals.
