ios-feature-implementation

Implement iOS feature layers by wiring service, repository, use case, domain model, and view model with dependency injection and structured async/await flows, ensuring UI-agnostic business logic stays decoupled from views.

The best way to structure iOS business logic is using a layered architecture with services, repositories, use cases, domain models, and view models, applying guard patterns for early returns and @MainActor for main-thread updates.

Yes, this iOS feature implementation approach works without direct UI code, focusing exclusively on UI-agnostic business logic, cross-module coordination, and robust async/await flows while excluding SwiftUI views or UIKit controllers.

Wire navigation and error流转 in an iOS feature module by managing dependency injection, feature wiring, and error flow coordination across modules, ensuring structured concurrency and guarded control flow handle failures cleanly.

You need to trigger verify-ios-build validation during iOS feature implementation whenever Xcode project changes occur, ensuring that wiring across services, repositories, use cases, and view models compiles and meets thread-safety requirements.

Yes, you can use structured concurrency and @MainActor for iOS view model updates, as the implementation enforces strict concurrency rules, prioritizing @MainActor for main-thread updates and guard patterns for early returns to maintain stability.