How ianfagundes/cosmonow works
Project Type and Purpose
• Type: Native iOS application
• Purpose: Display space imagery/video/info (Cosmo), allow CRUD on favorites, support offline cache, dark mode
• Architecture: Clean Architecture (Presentation, Domain, Data layers), MVVM, SOLID, Dependency Injection, Combine/Async-Await
File Structure
• Top-level “Presentation”, “Domain”, “Data”, “Infra” folders → classic layered separation
• “Presentation” subdivided into Views, ViewModels, Components (SwiftUI + Combine)
• “Domain” holds business entities and use-cases (GetCosmoUseCase) + protocols
• “Data” contains concrete Repositories/Services implementing Domain protocols
• “Infra” provides low-level implementations: network, cache, storage, media managers
• Tests mirror these layers (DataTests, DomainTests, PresentationTests)
Review README Insights
• Technologies: SwiftUI, Combine, Async/Await, URLSession, local caching (images, thumbnails, API data), DI
• Key features: fetching space data, thumbnails (YouTube), caching layers, favorites CRUD, error handling, dark mode
• Emphasis on modularity and testability
A. Frontend (Presentation Layer)
– SwiftUI Views (ContentView, CosmoView, CosmoDetailView, FavoritesView, MainTabView)
– ViewModels (CosmoViewModel, FavoritesViewModel, CachedImageViewModel)
– Reusable UI Components (FavoriteButton, DatePickerModalView, CachedAsyncImage, MediaView, ThumbnailView, YouTubeWebView)
B. Domain Layer
– Entities (CosmoModel)
– Use Cases (GetCosmoUseCase) + Protocols
C. Data Layer
– Repositories (CosmoRepository conforming to CosmoRepositoryProtocol)
– Services (CosmoService conforming to CosmoServiceProtocol)
D. Infrastructure Layer
– Network: NetworkManager, APIConfig, URLSessionProtocol, NetworkError
– Cache: DataCacheManager, ImageCacheManager, Youtube thumbnail cache
– Storage: FavoritesManager (persistent favorites)
– MediaManager (video playback support)
E. External Services
– Remote Space Data API (e.g., NASA)
– YouTube API (video thumbnails)
– Device Local Storage (UserDefaults, FileSystem)
Relationships & Data Flows
4) Repository delegates to Service or Cache:
• If cached data exists → return from DataCacheManager
• Else → NetworkManager → Remote API → parse into CosmoModel → store in cache → return
5) FavoritesViewModel uses FavoritesManager in Infra (persistent CRUD)
6) Media caching handled by ImageCacheManager / MediaManager → View renders via CachedAsyncImage, YouTubeWebView
7) Errors propagate back up to ViewModel for UI error states
Architectural Patterns & Principles
• Clean Architecture: strict layer boundaries and dependency inversion via protocols
• MVVM: separation between UI (Views) and state/business logic (ViewModels)
• SOLID + DI: each component has a single responsibility, injected via initializers
• Reactive & Async: Combine pipelines and Swift’s async/await for concurrency
• Caching strategy: multi-tier (API data, images, video thumbnails)
Required Elements for Clarity
• Optional: zoomed-in inset for critical flows (e.g., caching path)