swiftui-coding-guidelines

The best way to manage SwiftUI state is to enforce @StateObject for ownership and @ObservedObject for observation, avoiding unnecessary re-renders by preventing unstable identities and properly scoping state updates.

Implement SwiftUI navigation by using NavigationStack to manage routing from a List to a detail view, following structured patterns that standardize view composition and avoid common navigation anti-patterns.

Use Lazy stacks in SwiftUI when rendering long lists or complex grids to enforce performance practices, delaying view instantiation until needed and avoiding the computational cost of loading all rows simultaneously.

Common SwiftUI anti-patterns include using unstable identities in lists, overusing observation properties causing redundant re-renders, and nesting complex layouts without leveraging reusable view components.

Yes, you can use these SwiftUI coding guidelines for macOS app development, as they apply to iOS and macOS tooling across shared components like List, NavigationStack, and state management.

SwiftUI views re-render unnecessarily when using unstable identities or incorrectly applying @ObservedObject instead of @StateObject for ownership, causing the view hierarchy to rebuild upon external state changes.