swift-architecture-macos

Multi-window state synchronization with @Observable requires careful state ownership strategies to avoid shared state pitfalls. You implement per-window state isolation and window restoration patterns to ensure independent window contexts while maintaining reactive updates.

Bridging SwiftUI with AppKit uses NSViewRepresentable to embed AppKit views in SwiftUI and NSHostingController to embed SwiftUI in AppKit. These patterns enable interoperability while maintaining architectural boundaries and preventing common integration bugs.

Managing NSDocument workflows involves subclassing NSDocument, handling window controller management, implementing autosave, and validating menus. You coordinate these with SwiftUI app lifecycle hooks to maintain production-grade document-based app architecture.

Dependency injection with @Observable uses environment-based patterns to provide testable services like analytics and printing. You inject dependencies through the SwiftUI environment to maintain separation of concerns and support testing across view models.

Yes, the architecture patterns explicitly support building professional document editing apps with multiple inspector windows, proper undo/redo support, and testable dependency injection. The recipes cover NSDocument persistence and multi-window state management.

Common macOS architectural pitfalls include incorrect state ownership across multiple windows, improper AppKit automatic recomposition, and technical debt from poorly bridged SwiftUI-AppKit components. Production-ready patterns provide constraint documentation to avoid these issues.