swiftui-ui-patterns

Use one NavigationStack per tab, each bound to its own router object holding a path array of Hashable route enums. Inject the router into the environment so child views navigate programmatically, and centralize destination mapping with a single navigationDestination modifier.

Use @State for local value state owned by one view, @State with an @Observable type for root-owned reference models on iOS 17+, and @Environment for shared app services. Reserve @StateObject and @ObservedObject for iOS 16 and earlier, and @EnvironmentObject only for truly shared app-level state.

Define an Identifiable SheetDestination enum, store the current sheet on a router object, and map destinations to views with a sheet(item:) modifier. Child views set router.presentedSheet directly, and sheets own their actions by calling dismiss() internally.

Yes, the patterns call out minimum OS requirements and provide fallbacks. When the Observation API from iOS 17 is unavailable, use ObservableObject with @StateObject at the root and @ObservedObject for injected models.

Janky scrolling usually comes from unstable ForEach identity, expensive work inside body, or overly broad observation scope. Give rows stable IDs, move sorting and formatting out of body, and use lazy containers like List or LazyVStack for large collections.

Bind searchable(text:) to local state and use .task(id: query) so the task restarts on each change. Sleep briefly inside the task, check Task.isCancelled, and skip empty queries to avoid firing a network request per keystroke.