How kudoleh/ios-clean-architecture-mvvm works
Main Components Identification
a) Domain Layer (Core Business Logic)
• Entities (Movie, MovieQuery)
• Use Cases (SearchMoviesUseCase, FetchRecentMovieQueriesUseCase)
• Repository Interfaces
b) Data Layer
• Repository Implementations
• Network Services
• Persistent Storage (CoreData, UserDefaults)
• Data Transfer Objects (DTOs)
c) Presentation Layer
• MVVM Components (ViewModels, Views)
• Flow Coordinators
• UI Components
┌─────────────────────────────────────────────┐
• Presentation Layer │
• ┌─────────────┐ ┌──────────┐ ┌──────────┐ │
• Views │ │ViewModels│ │ Flows │ │
• ┘ └──────────┘ └──────────┘ │
• ┘
• ▲
• (Depends on)
┌─────────────────────────────────────────────┐
• Domain Layer │
• ┌─────────────┐ ┌──────────┐ ┌──────────┐ │
• Entities │ │Use Cases │ │Repository │ │
• ┘ └──────────┘ │Interfaces │ │
• ┘ │
• ┘
• ▲
• (Depends on)
┌─────────────────────────────────────────────┐
• Data Layer │
• ┌─────────────┐ ┌──────────┐ ┌──────────┐ │
• Repository │ │ Network │ │Persistent│ │
• Impl │ │ Service │ │ Storage │ │
• ┘ └──────────┘ └──────────┘ │
• ┘
Detailed Component Relationships
• Data flow between components
• Dependency injection paths
• Repository pattern implementation
• MVVM binding relationships
• Flow coordinator navigation paths
Special Features to Highlight
• DIContainer structure
• Flow Coordinator pattern
• Data binding mechanism using Observable
• Caching mechanism
• Error handling flow
Implementation Details
Technical annotations for:
• SwiftUI/UIKit view implementations
• CoreData storage
• Network layer implementation
• DTO mapping
• Unit test coverage