swiftui-patterns

Reduce unnecessary SwiftUI view re-renders by adopting the @Observable macro and structuring view models so subviews only invalidate when the specific data they read changes. This narrows the invalidation scope to views actively consuming updated state.

Build type-safe SwiftUI navigation by routing with NavigationStack and NavigationPath using an explicit destination model. This approach replaces string-based routing with predictable, compile-time checked navigation flows.

Migrate from ObservableObject to the Observable framework by replacing ObservableObject conformances with the @Observable macro, updating property wrappers, and composing smaller subviews to minimize invalidation scope during state updates.

SwiftUI list rendering becomes slow when expensive work executes inside the body. Optimize performance by using lazy containers, stable identifiers, and reducing invalidation scope to prevent unnecessary recalculations during scrolling.

Yes, these SwiftUI architecture patterns apply to both iOS and macOS apps. The state management, view composition, and NavigationStack routing techniques target responsive UI requirements across Apple platforms.

Avoid using @Observable in SwiftUI when integrating with older codebases that still rely on ObservableObject, as the frameworks have different invalidation behaviors. Stick with ObservableObject where legacy compatibility is required.