swift

Structure Swift architecture by routing dependencies UI/ViewModel -> UseCase -> Repository -> DataSource. This enforces clean boundaries and explicit concurrency safety using async/await and Actors for Swift 6 strict concurrency scenarios.

A Swift UseCase should expose a single public function, func execute() async -> Result<T, Error>. Dependencies must be injected into the UseCase rather than accessing repositories directly, mapping repository errors to Result types.

Decouple Swift Repositories and DataSources by making DataSources depend on external APIs while Repositories depend on DataSources. Repositories should expose raw data types via async throws, ensuring strict dependency boundaries and testability.

Yes, Swift 6 strict concurrency requires @Sendable closures to ensure thread safety. You should use Swift Concurrency async/await patterns and Actors for shared state to maintain explicit concurrency safety across architectural layers.

Internal errors leak to the UI when architectural boundaries are violated. UseCases must map repository errors to Result<T, Error> types, establishing explicit error handling boundaries that prevent DataSource internal errors from reaching the UI layer.