ios-ui

Layout issues in SwiftUI often stem from view identity problems or missing LazyVStack optimization; in UIKit, check constraint conflicts and priority ordering. Domain-specific fixes address these root causes before profiling, improving performance and eliminating flicker.

Navigation issues typically involve incorrect view hierarchy, state management misalignment, or routing logic errors. Domain-focused debugging routes to the specific problem area—SwiftUI state, UIKit controller stack, or transition logic—for faster resolution.

Yes. Accessibility guidance covers both frameworks, addressing VoiceOver compatibility, semantic hierarchy, and design guidelines. The Skill routes accessibility issues to framework-specific fixes that ensure WCAG compliance across your codebase.

Liquid Glass and other design systems require consistent implementation across SwiftUI and UIKit components. The Skill provides domain-specific guidance and routes to design-system handlers that align your UI with modern iOS visual standards.

Sluggish or flickering UI usually indicates rendering inefficiency or state thrashing. Start with domain-specific fixes like LazyVStack optimization or constraint simplification before profiling; the Skill routes you to the likely culprit in SwiftUI or UIKit.

It handles both. The Skill routes iOS UI issues across SwiftUI, UIKit, layout constraints, navigation, animations, and accessibility, applying domain-specific fixes tailored to whichever framework your code uses.