swiftui-expert-skill

SwiftUI state management requires choosing property wrappers based on data scope and ownership. Use @State for local view state, @Binding for sharing mutable state, and @Observable for complex model objects to prevent common bugs and redundant updates.

Optimizing SwiftUI performance involves applying actionable patterns for view composition and list rendering. Minimizing redundant state updates and adhering to Apple's latest API design patterns ensures efficient view updates across various iOS deployment targets.

The guidance supports iOS 26+ Liquid Glass styling by providing modern API adoption patterns. It ensures codebases remain current by implementing Liquid Glass styling with appropriate fallbacks for older deployment targets.

You can use this guidance to review and refactor existing iOS user interfaces. It provides expert recommendations for refactoring views, identifying potential performance bottlenecks, and suggesting state management improvements.

SwiftUI refactoring can fail accessibility standards if architectural neutrality is compromised. Adhering to Apple's latest API design patterns and accessibility standards while maintaining architectural neutrality ensures compliance during view composition.

You should avoid using @Observable for simple, local view state where @State is sufficient. Overusing @Observable can introduce unnecessary complexity; choosing the correct property wrapper prevents common bugs and maintains performance.