My MacBook contains almost nothing but development tools and related data, and I’ve long maintained at least 500–600 GB of free space. For quite some time, I assumed its internal storage was more than sufficient. But coding agents have changed that. Last week, I found myself in the rather embarrassing situation of having my disk space rapidly exhausted—not once, but twice.
As AI coding becomes widespread, more and more developers lean toward one view: imperative frameworks like UIKit may suit coding agents better than SwiftUI. The reasoning is intuitive. UIKit's logic is direct and explicit: create objects, set properties, add them to the hierarchy, build constraints. Every step acts on a concrete entity. SwiftUI, by contrast, tucks much of its implementation detail behind declarative syntax, where state, environment, identity, layout, and rendering jointly determine the final result.
Xcode 26.3 marked the first time Apple opened its own capabilities to external agents through MCP. Many of those capabilities were already reachable through the CLI, but Preview rendering was entirely new. Xcode 27 went a step further with a headless MCP server, making these tools even easier to call, so I wove Preview rendering deeply into my AI workflows. Along the way I ran into a few pitfalls, and came away with some reflections and hopes.
In the first time I saw the `ArrangementView` API, I had a vague sense of discomfort, though I couldn’t quite put my finger on why. It wasn’t until I actually used it in Xcode 27.1 beta that the feeling began to take shape. After reading more of Apple’s materials and putting the API back into the context of the iPhone Duo, I realized that this discomfort came from two places. Part of it was simply that I hadn’t understood where the API was meant to fit; once I did, that part made sense. The other part came from the API itself—and remained even after I understood its design.
Apple has released the 27.2 beta. Although the iPhone Duo simulator is still missing, the new `project.xcproj` is quite eye-catching. It replaces the `project.pbxproj` build graph inside the `.xcodeproj` bundle, not the entire project bundle. What are its highlights, what problems does it solve, and what remains unchanged? This article will explore these aspects.
Once a dataset grows large, SwiftData lists start to stutter. This has been the performance complaint I've heard most often these past few years. Once you actually spend time on it, you find that the slowness isn't only the long initial load — the enormous memory footprint drags performance down just as much. This article looks at why these problems show up in SwiftData, and where to start fixing them.
From Q&A and code generation to letting agents take on more complete pieces of work, I have now been using AI for several years.
How to build a trusted AI collaborator? Discover "delegatability" using a deterministic runtime and external docs, featuring a practical Task-Driven workflow guide.
In WWDC 2026, Apple engineers introduced a new SwiftUI feature — ContentBuilder. From the usage perspective, it seems to be nothing more than a ViewBuilder with a wider scope. Apple also claims this adjustment can significantly improve type-checking performance. This article will dissect the essence of ContentBuilder and explore the secrets behind the performance boost.
SwiftUI layout and animation are powerful because they combine view identity, container negotiation, transactions, geometry, and rendering rules. This collection gathers foundational explanations and practical examples for layout priority, GeometryReader, safe area, ScrollView, overlay/background, spacing, and animation behavior.
CloudKit lets Apple platform apps store, sync, and share data through iCloud. This collection maps the practical choices across Core Data with CloudKit, iCloud Documents, NSUbiquitousKeyValueStore, sync-status handling, and multi-device data architecture for indie and small-team apps.
SwiftUI data flow depends on well-placed sources of truth, property wrappers, Observation, and architecture boundaries. This collection organizes articles from @State, @Binding, @StateObject, @ObservableObject, AppStorage, and Observation to larger app architecture and cross-platform state management.
SwiftUI's declarative model is productive, but its update pipeline, identity rules, lazy containers, and animation behavior can make performance and debugging work feel opaque. This collection gathers articles on view updates, lifecycle, optimization patterns, diagnosis, and real bug analysis for SwiftUI apps.
Core Data and SwiftData are the core persistence stacks for Apple apps. This collection connects modeling, relationships, predicates, transactions, concurrency, persistent history tracking, and migration-oriented thinking, helping readers compare the two frameworks beyond basic CRUD usage.