Sign in Subscribe

Vadims Krutovs

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

WebPage: iOS 26’s Headless, Observable Browser — No UIKit Required

Most apps that need to load a web page reach for WKWebView wrapped in a UIViewRepresentable — a layer of UIKit glue that was never pleasant to write and became less defensible with every SwiftUI release. iOS 26 ships a cleaner answer: WebPage, a fully @Observable model object that loads URLs,

Stress-Test Your SwiftUI Accessibility in a Single Preview

Most iOS developers test accessibility one setting at a time: flip Bold Text on, check the layout, flip it off, bump Dynamic Type up, check again. The problem is that your users don't toggle one setting in isolation — they set up their device once and forget about it.

Stop Writing the Same SwiftData Code Twice

There's a pattern I kept writing. Fetch, insert, save. Fetch, insert, save. Sometimes with a predicate, sometimes with a sort descriptor, but always the same shape. I'd finish a model, open a new feature file, and before I'd written a single line of business

I Switched from OpenAI Codex to Claude Code — Here's Why

I was a Codex user. It was my daily driver for iOS development, and I was happy with it. Then I decided to give Claude Code a proper try — and I'm not going back. Here's what changed my mind, and where Codex still has an edge.

Escaping Query: Building a Testable LiveQuery Property Wrapper

Introduction SwiftData is great — until it isn’t. When Apple introduced SwiftData and the @Query macro, it felt like the missing piece for persistence in SwiftUI. Clean syntax, automatic updates, no boilerplate. But there was a clear limitation baked into its design: All persistence logic was forced to live inside