swiftui-patterns

Define an @Observable final class as your view model and hold it in the view with @State. SwiftUI tracks property-level changes, so only views reading a changed property re-render, replacing the older ObservableObject and @Published approach.

@State holds view-local value types like toggles, @Binding creates a two-way reference to a parent's @State, and @Observable classes manage models with multiple properties. Use @Bindable when you need two-way binding to an @Observable property.

Create a Router class holding a NavigationPath and define a Hashable enum for destinations. Bind the path to NavigationStack and map destinations with .navigationDestination, enabling programmatic push and popToRoot navigation.

No, new code should use the @Observable macro instead of ObservableObject, @Published, @StateObject, and @EnvironmentObject. The Observation framework provides finer-grained change tracking so only affected views re-render.

Slow scrolling usually comes from eager rendering, unstable identifiers, or expensive modifiers. Use LazyVStack inside ScrollView, provide stable unique IDs in ForEach, and minimize .shadow(), .blur(), and .mask() in list rows.

Never perform I/O, network calls, or heavy computation inside body, since it runs on every re-render. Use .task {} for async work, which starts when the view appears and cancels automatically when it disappears.