What problem does it solve?
Provides concrete guidance to structure SwiftUI views, manage state ownership, and compose view hierarchies so apps remain performant, testable, and easy to maintain across iOS 26+ and Swift 6.3. It reduces ambiguity about when views should own state versus when shared models belong in the environment, and it prescribes modern async loading and lifecycle patterns to avoid common UI bugs and performance regressions.
Core Features & Use Cases
- Architecture guidance: Default Model-View (MV) pattern, app wiring, dependency graph modifier, and lightweight client patterns for network and service layers.
- State management rules: Ownership conventions for @State, @Bindable, let, @Environment, and @Observable with explicit @MainActor guidance.
- View composition & performance: Decompose large views, use Lazy stacks/grids, prefer stable Identifiable IDs, and create custom ViewModifiers for repeated styles.
- Async & lifecycle: Use .task and .task(id:) for cancellable async loading, prefer .sheet(item:) for modal presentation, and avoid manual Task creation in onAppear.
- Migration & review: Migration mappings from older APIs (ObservableObject, NavigationView) and a review checklist to validate HIG alignment, accessibility, and stability.
- Use case example: Implement a Feed screen that injects a client from the environment, loads posts with .task, displays results in a lazy list, and follows @Observable ownership rules.
Quick Start
Create a SwiftUI FeedView targeting iOS 26 that uses the MV pattern, injects a FeedClient via the environment, loads posts in .task, displays them with a LazyVStack or List using stable Identifiable IDs, and ensures @Observable view models are @MainActor-isolated.
