guide-swiftui-ui-patterns

SwiftUI state ownership requires choosing the narrowest state tool like @State, @Binding, or @Observable to prevent rerenders. This guide provides best-practice patterns for selecting the correct wrapper based on view hierarchy and data-flow needs.

SwiftUI navigation and sheet presentation should use NavigationStack and enum-driven sheets to reduce prop-drilling and modal conflicts. This guide recommends practical routing approaches using TabView-based architectures and item presentation conventions.

Refactoring SwiftUI views for component composition involves structuring screens with small focused subviews and declarative hierarchies. This guide provides patterns to break down complex views into reliable, maintainable components.

Use @State for local view ownership and @Environment for shared data across the view hierarchy to avoid ownership bugs. This guide helps determine the narrowest appropriate SwiftUI state tool for your specific data-flow scenario.

Yes, this SwiftUI pattern guide covers responsive layout rules using stacks, grids, and OS-appropriate APIs. It encourages reliable layout strategies for building screens that adapt correctly across different device sizes.

Handling async lifecycle and scroll-driven reveals in SwiftUI requires following specific rules for state wrappers and presentation conventions. This guide provides battle-tested patterns for managing these behaviors reliably during screen builds.