How berrrchik/cocktailfinder-swiftapp works
Project Type and Purpose
• Mobile client application (iOS app) using SwiftUI and MVVM
• Purpose: allow users to search, view, favorite and filter cocktail recipes by consuming TheCocktailDB REST API, with offline caching and persistence of favorites
High-Level Architecture Components
• Presentation Layer
– Views (SwiftUI): SearchView, RecipeView, FavoriteCoctailsView, FilterView, RandomCocktailView, CocktailCardView, StateView components
• Presentation Logic
– ViewModels (Combine): SearchViewModel, FilterViewModel, RecipeViewModel, RandomCocktailViewModel, CocktailCardViewModel, FavoritesViewModel
• Domain Model
– Model structs: Cocktail, FilterCategory, FilterOption
• Services Layer
– APIService: handles HTTP requests to TheCocktailDB API via URLSession and JSON decoding
– CocktailCacheService: in-memory or on-disk caching of popular/random cocktails
– FavoritesService: persistence of favorite cocktails in UserDefaults
• External Dependencies
– TheCocktailDB API (external REST service)
– SDWebImageSwiftUI (asynchronous image loading)
• Local Storage
– UserDefaults (favorites), optional on-disk cache for images/data
Relationships and Data Flow
1. User taps UI in a View → ViewModel receives action
2. ViewModel invokes Services (APIService or FavoritesService/CocktailCacheService)
3. Service makes network call or reads/writes UserDefaults
4. Service returns data (Combine publisher or callback) → ViewModel processes and publishes state
5. View observes ViewModel’s published properties → updates UI
6. Image loading flows from URL through SDWebImageSwiftUI to Image view
Architectural Patterns and Design Principles
• MVVM: clear separation of UI (View), presentation logic (ViewModel), and data (Model + Services)
• Single responsibility: each Service handles one concern (network, caching, favorites)
• Dependency injection (pass APIService into ViewModels)
• Reactive data flow via Combine