SwiftUI

I wanted a simple behaviour in a SwiftUI app: tap Add, a new row slides into the list, and then the editor for that row pushes onto the navigation stack. Two animations, one after the other. It took a detour through a surprising withAnimation behaviour and a small race condition to get Read more

When building SwiftUI applications, it is easy to default to adding mutable boolean flags onto domain models. On paper, adding var isFavorite: Bool to a Recipe struct feels natural. In practice, it entangles domain content with user presentation state, triggers unnecessary view invalidations, and complicates syncing with persistent storage. Here is an architectural walkthrough Read more

In the classic WWDC 2020 session “Data Essentials in SwiftUI” (around timestamp 4:18), Apple presented a core architectural pattern for managing complex form state: the EditorConfig struct. The speaker highlights why wrapping form data into a value type is so powerful: “EditorConfig can maintain invariants on its properties and be tested independently. And because Read more

When managing modal presentation in SwiftUI, developers frequently face a dilemma between direct boolean bindings (.sheet(isPresented:)) and item bindings (.sheet(item:)). While .sheet(item:) binds presentation directly to optional data, it presents architectural trade-offs: the item passed to the sheet content closure is immutable value data, meaning two-way editing requires workarounds like class reference Read more

When profiling SwiftUI view trees with Self._printChanges(), child views receiving projected bindings ($) through intermediate wrappers like @StateObject, @ObservedObject, or @Bindable exhibit a unique lifecycle pattern on their first parent state update. Only projected bindings created directly off @State bypass this first-toggle re-render. Here is a minimal reproducible test case documenting the exact behavior, memory addresses, and Read more

If you have ever built an edit flow in SwiftUI using .alert(item:) or .sheet(item:) backed by an ObservableObject, you have almost certainly bumped into a frustrating wall: modifying a property in one TextField inside the alert doesn’t update another TextField or view sitting right next to it. Here is a deep dive into why this happens, why modern solutions like @Bindable work Read more

If you spent years building software in UIKit, AppKit, Android XML/Views, or even the traditional DOM, your brain has been hardwired around a single, foundational assumption: a view is a long-lived object residing at a stable address in memory. In traditional Object-Oriented UI paradigms, UI components are stateful instances of reference Read more