swiftui-patterns

State management in SwiftUI with @Observable involves replacing ObservableObject conformances with the Observation framework. You inject @Observable view models into the @Environment to trigger efficient view updates automatically when accessed properties mutate.

Type-safe navigation in SwiftUI is best implemented using NavigationStack with NavigationPath. This approach allows you to manage routing data using value types, enabling predictable state-driven navigation and simplified deep linking.

Optimizing SwiftUI performance for large lists requires using lazy containers like List or LazyVStack, ensuring stable identifiers for data items, and avoiding expensive computation or unnecessary state access directly within view bodies.

Use @State for local view-internal state ownership, and @Binding to pass mutable state references down to child views. This ensures proper source-of-truth management and maintains efficient view composition without redundant data duplication.

Yes, this SwiftUI architecture guidance applies to macOS development and other Apple platforms. The patterns for state management, view composition, and performance optimization are universal across declarative UI development environments.

Excessive view body recomputation during state updates happens when views unnecessarily access mutable state or perform expensive work directly in the body. Extracting subviews and restricting state access to @Observable properties resolves this.