iOS Resources
Hand-picked Articles and Videos

A deep dive into Apple's standardized component for empty, unavailable, or failed content states. Before iOS 17, every app built the same VStack with an icon, title, description, and button. ContentUnavailableView provides a canonical system component with platform consistent styling, accessibility defaults, and Dynamic Type support. The article covers basic usage with title and systemImage, the built in search variant (ContentUnavailableView.search), custom initializers with view builders for actions (like a retry button for network failures), real world production examples (failed requests, first time UX, empty invoices), accessibility considerations, state driven patterns with enum based loading states, common mistakes (overbuilding, generic messages, missing recovery actions, showing empty state during loading), and when not to use it (onboarding, paywalls, interactive tutorials).

Building an event bus for communication between loosely coupled parts of an app. The implementation focuses on type safety (events conform to a marker protocol), thread safety with NSLock, automatic cleanup when the subscriber is deallocated, explicit cancellation via SubscriptionToken, MainActor delivery for UI code, and AsyncStream support. The key design choice is that subscriptions follow the owner's lifetime (weak reference), not the token's. The bus cleans up dead subscriptions lazily during publish or subscribe operations. Publishing creates a snapshot of subscribers and delivers events synchronously outside the lock.

A detailed breakdown of five core SwiftUI gestures. TapGesture with count and coordinateSpace parameters. LongPressGesture with minimumDuration, onPressingChanged, and maximumDistance. DragGesture with .onChanged, .onEnded, and an advanced version using .updating with @GestureState, explaining value, state, and transaction parameters. MagnifyGesture with magnification and velocity. RotationGesture using two @State properties (currentAngle and finalAngle) to preserve rotation after the gesture ends. A separate section on gesture composition: .map for transforming data, .simultaneously for parallel execution (unwrapping optional .first and .second), and .sequenced for sequential gestures (switch statement on the enum).

A straight introduction to SwiftData, Apple's persistence framework for iOS 17. You will see how to define models with @Model, set up a model container, fetch data with @Query, insert and save via modelContext, filter with #Predicate, and link models with @Relationship. The code is minimal and clean.

A comparison of two parallel implementations of the same iOS feature. Team A used PRD driven AI TDD with test first development and an adversarial "convince me this is correct" review. Team B used a human in the loop iterative approach: write code, run it, hit edge cases, refactor. Expected A to be tighter and more correct. The opposite happened. B won on three of four dimensions. A was cleaner on architecture only. B had stronger tests (golden binary fixtures, integration invariants), better threading correctness (assert(!Thread.isMainThread)), production observability (logging, performance tracking), and documentation with rationale per decision. Five mechanisms explain the gap. TDD does not generate the highest leverage tests (golden fixtures require working code first). Spec plus test creates a closed loop where no one asks "what about interactions?" TDD is hostile to instrumentation because logs and tracking have no failing test. Adversarial review hardens claims but does not reframe scope. Micro commits make the refactor step invisible and easy to skip.

The article explains that @Environment(.scenePhase) works reliably only in a pure SwiftUI app with SwiftUI lifecycle. When a SwiftUI view is hosted inside UIKit via UIHostingController, scenePhase may not behave as expected because the view does not participate in SwiftUI's scene model. The recommended alternatives are observing UIApplication notifications (didBecomeActiveNotification, willResignActiveNotification) for app wide state, or UIScene notifications (didActivateNotification, willDeactivateNotification, didEnterBackgroundNotification, willEnterForegroundNotification) for scene level behavior closer to scenePhase semantics.

The article presents a layered approach to iOS performance. It covers product level (perceived performance, optimistic updates, testing under Low Power Mode), metrics and observability (user centric metrics, breaking down latency, local vs production monitoring), architecture and data flow (reducing dependency breadth, critical path), UI and rendering pipeline (body execution cost, update frequency, scrolling, layout strategy), network and backend (round trips, request orchestration, concurrency), data and caching (reuse over recomputation, prefetching, cache layers), energy and power (continuous work, background activity), concurrency and scheduling (main thread, priorities, task structure), algorithms and data structures (complexity, access patterns, branching), memory and representation (heap allocations, copying, data layout), and CPU and hardware (branch prediction, cache, instruction level parallelism). The article emphasizes starting from user perception and moving down the stack, not micro optimizing prematurely.

The article explains how to style macOS window toolbars in SwiftUI on macOS 26. It covers toolbar layout and size (default unifiedCompact, expanded with title on its own row), hiding the window title (toolbar removing .title or showsTitle false), hiding the title bar (windowStyle .hiddenTitleBar), clearing the toolbar background (toolbarBackgroundVisibility .hidden, toolbarBackground .hidden or .clear), setting a custom toolbar background color with toolbarColorScheme, and controlling toolbar visibility (toolbarVisibility .hidden, windowToolbarFullScreenVisibility .onHover).