ios-swift-expert

SwiftUI apps require MVVM architecture with @StateObject for view models, @Published properties for reactive updates, and async/await for memory-safe data loading. Combine state management with proper error handling to keep UI responsive and data consistent across view lifecycle.

Swift's modern concurrency prevents common memory issues through type safety and structured concurrency patterns. Use async/await instead of completion handlers, avoid strong reference cycles with [weak self] capture lists, and let Swift's ownership system enforce memory safety automatically.

Yes, hybrid SwiftUI and UIKit development is fully supported. Use UIViewControllerRepresentable to wrap UIKit controllers in SwiftUI, or NSViewControllerRepresentable on macOS. This lets you migrate incrementally while leveraging both frameworks' strengths.

Core Data stores persistent data while Combine publishes changes reactively. Use @FetchRequest in SwiftUI to fetch and observe Core Data changes, or combine NSFetchedResultsController with Combine publishers for manual control over data updates and UI binding.

Xcode includes Instruments for profiling memory, CPU, and frame rates, plus SwiftUI previews for rapid iteration. Use the debugger, breakpoints, and console logging to trace execution. Profile with Xcode's built-in tools to identify bottlenecks before shipping.

Use VoiceOver support, dynamic type sizing, and semantic accessibility labels in SwiftUI. Localize strings with Localizable.strings files and region-aware formatting. Test with Xcode's accessibility inspector and simulator to verify compliance with Apple design guidelines.