How luannluna/animeverse works
Project type and purpose
• AnimeVerse is a native iOS mobile application built with SwiftUI.
• It serves as a front-end for discovering, searching, and managing anime, consuming the AniList GraphQL API, caching images with Kingfisher, and persisting favorites locally (SwiftData) and via Firebase.
File structure
• Top-level modules:
• AnimeVerse/ — the main SwiftUI app target
• AnilistAPI/ — generated Apollo GraphQL client code
• AnimeVerseTests/ & AnimeVerseUITests/ — test targets
• Inside AnimeVerse/:
• Components/ — reusable SwiftUI views
• Scene/ — feature-organized screens (Home, Search, Details, Favorites, Profile, SavedList) each with a View and ViewModel
• Navigation/ — global Router and AppRoute definitions
• Services/ —
– AnilistService (networking, cache)
– FirebaseService (auth, user, watching list)
– LocalUserStore, UserSession
• Models/ — domain data structures and DTOs
• GraphQL/ — .graphql query files (source of generated code)
• Extensions/, Helper/, Utilities/ — supporting code
• Config & schema at root: SwiftLint, Apollo config, GraphQL schema files.
Insights from README
• Confirms tech stack: SwiftUI, Apollo iOS, Kingfisher, SwiftData, AniList API, Firebase.
• Mentions offline support (favorites stored locally).
• Emphasizes smooth UI and fast GraphQL queries.
a. Main components
1. SwiftUI App Layer
• Scenes & Components (UI Views)
2. Presentation Layer
• ViewModels (one per Scene)
3. Domain/Service Layer
• AnilistService (ApolloClient wrapper, cache service)
• FirebaseService (Auth, Firestore user and list)
• LocalUserStore & SwiftData persistence
4. Data Layer
• AnilistAPI module (generated GraphQL types & operations)
5. External Services
• AniList GraphQL API endpoint
• Firebase Authentication & Firestore
b. Relationships & dataflow
• User taps UI → View (ViewModel) → calls Service
• Service issues GraphQL query via ApolloClient (AnilistAPI) → AniList API → JSON response → decoded to Swift models
• Service updates local SwiftData store for favorites or calls FirebaseService for remote sync
• Kingfisher image loader fetches & caches cover images from AniList CDN
• Navigation flows managed by Router, transitioning between Scenes
c. Architectural patterns & principles
• MVVM: Views bind to ViewModels, which orchestrate Services
• Clean layering: UI → Presentation → Domain → Data
• Dependency injection via Router and Service singletons/UserSession
• Offline‐first design for favorites
• Modularity: separate GraphQL codegen (AnilistAPI) from app code
d. Key technologies
• SwiftUI (UI layer)
• Apollo iOS & generated AnilistAPI (GraphQL client)
• Kingfisher (image caching)
• SwiftData (local persistence)
• Firebase Auth & Firestore (user identity & list sync)