How denissimon/cryptocurrency-info works
Project type and purpose
• This is a single-platform (iOS) mobile application built in Swift.
• It displays cryptocurrency data (prices, profiles, conversion rates) retrieved from external APIs (Messari API and a currency conversion service).
• Architectural style: Layered Architecture with MVVM-Coordinator (MVVM-C) pattern, dependency injection, data binding (Observable/Event), and configurable persistence (UserDefaults or SwiftData).
File structure
Top-level directories and their roles:
• Common: application scaffold (AppDelegate, configuration, shared utilities, data binding/events)
• Coordinator: flow controllers and DI container for wiring and navigation
• Data: abstraction interfaces, network interactors, API definitions, persistence adaptors, repository implementations
• Modules: feature modules (AssetsList, AssetDetails), each containing View, ViewModel, Models, and storyboards
• Services: cross-cutting service (currency conversion)
• Tests: unit and UI tests
Configuration files: Xcode project files, Info.plist, Package.resolved, etc.
README for insights
• Confirms use of MVVM-C, Layered Architecture, Swift Concurrency (async/await), URLSessionAdapter, SwiftEvents for data binding, Toast-Swift for UI feedback, UAObfuscatedString for string obfuscation.
• Two feature modules: AssetsList (paging list of cryptocurrencies) and AssetDetails (detailed view per asset).
• Repositories abstract data sources. DIContainer wires interfaces to concrete implementations (network vs persistence).
Detail
• Every major class or component group (View, ViewModel, Coordinator, Repositories, Interactors, DIContainer).
• Explicitly show the two persistence options (SwiftDataAdapter vs UserDefaultsAdapter) converging on SettingsRepository.
• Shared events mechanism between modules if used.