Sign in Subscribe

iOS

A collection of 12 issues

SwiftUI's alert(item:) and confirmationDialog(item:): No More Fake Identifiable Structs

Every item-driven presentation in SwiftUI used to come with a tax: your model had to conform to Identifiable. sheet(item:), popover(item:), fullScreenCover(item:) — all of them take a Binding<Item?>, but only if Item can hand back a stable id. For a throwaway struct built for

EmptyModifier in SwiftUI: Debug-Only View Modifiers That Vanish From Release Builds

Every SwiftUI codebase collects a few view modifiers that should only exist during development: a red border around a view that's fighting the layout system, a caption showing a view's live frame size, an overlay flagging which cell came from a mock network response. The obvious

visualEffect in SwiftUI: Scroll-Driven Effects Without GeometryReader Breaking Your Layout

You want a photo to fade and shrink as it scrolls off the top of the screen. The instinct, drilled in by years of SwiftUI tutorials, is to wrap it in a GeometryReader, read the frame, and drive the effect from there. Then your layout falls apart: the cards collapse

geometryGroup() in SwiftUI: Why Your Custom Animation Curve Gets Ignored

You wired up a phaseAnimator to shake a button when a form fails validation, and you wrote a short, sharp .linear curve in the animation: closure so the shake feels mechanical. You run it — and the button springs instead. Soft, bouncy, completely wrong. The curve you asked for is being

Why Your @Observable View Isn't Updating: SwiftUI Tracks Reads, Not Writes

A property changes and the view doesn't move. You can log the new value, you can watch it tick over in the debugger, but the UI keeps showing the old one. There's no crash, no console warning, no purple runtime issue — and the line that should

SwiftUI View Identity: Why an If Statement Breaks Your Animations

You add a conditional to a view — highlight a selected cell, dim an archived row — and reach for the tool every Swift developer knows: an if statement. The code compiles, the logic is correct, and yet the result is subtly wrong. The animation snaps instead of glides, or a text

onScrollGeometryChange: Track Scroll Position in SwiftUI Without Tanking Performance

For years, reading a scroll view's offset in SwiftUI meant the same awkward dance: drop a GeometryReader into the content, publish the frame through a PreferenceKey, define a custom coordinate space, and read it all back out somewhere up the tree. It worked, but it added phantom views

Branching Haptics in SwiftUI: Getting More Out of sensoryFeedback

Most apps reach for sensoryFeedback exactly once and wire it to a single outcome: a button tap plays .impact, a save plays .success. That works, but it leaves most of the API on the table. The modifier was built to branch — one declaration can pick a different haptic for success,

Per-Glyph Text Animation in SwiftUI with TextRenderer

Text animation in iOS has always been awkward. To animate individual characters — a wave effect, a staggered entrance, per-letter color shifts — you either dropped into UIKit with NSTextStorage and CALayer gymnastics, or built a fragile HStack of individual Text views and lost kerning and line-wrapping in the process.

ContainerValues: Per-Item Customization in SwiftUI Containers

If you've ever needed one child view in a SwiftUI container to look or behave differently from its siblings, you've probably reached for @Environment — and paid the price. Environment values propagate to every descendant in the subtree, not just the direct children of your container. Set