How genti2024/genti-android works
Project type and purpose
• This is a multi-module Android application (“Genti”) built with Clean Architecture and MVI using Jetpack Compose.
• Its purpose is to let users create AI-generated photos, manage them in a feed/profile, handle onboarding, in-app purchases, and receive push notifications.
High-level architectural layers
• Presentation Layer (app + feature modules)
• Domain Layer (business rules, use cases)
• Data Layer (repositories, data sources, DTOs, network & local modules)
• Core Modules (shared utilities: common, design system, navigation, network, datastore)
• Build-logic (custom Gradle convention plugins)
• External Services (backend API, AWS S3, Firebase, Google Play Billing, Kakao Open API, Amplitude)
Main components
a. App Module
• Contains Android entry point, Hilt setup, Manifest, UI host (MyApp.kt)
• Depends on feature modules and core modules
b. Feature Modules (presentation for each screen flow)
• onboarding, main, feed, generate, profile, result, setting
• Each feature contains ViewModel (MVI intents, states, side-effects), Compose screens, navigation graph
c. Domain Module
• Contains UseCase classes and Repository interfaces
• Defines data models (entity/request/response) and business logic contracts
d. Data Module
• Implements Domain repositories (AuthRepositoryImpl, FeedRepositoryImpl, etc.)
• Contains DataSources (remote via Retrofit, local via SharedPrefs), DTOs, Service interfaces
• Uses core/network for Retrofit, core/datastore for SharedPref
e. Core Modules
• common: extensions, managers (ImageManager, PermissionManager, AmplitudeManager)
• designsystem: UI components (buttons, dialogs, themes)
• navigation: centralized route definitions
• network: RetrofitModule, AuthInterceptor
• datastore: Hilt modules for SharedPref
f. External Services
• Backend REST API (hosted service endpoints)
• AWS S3 (presigned URL upload)
• Firebase Cloud Messaging (push notifications)
• Google Play Billing API
• Kakao Open API (login)
• Amplitude (analytics)
Relationships and interactions
• Presentation → Domain: feature ViewModels invoke UseCases
• Domain → Data: UseCases call Repository interfaces
• Data → Core Network/Datastore: DataSources use RetrofitModule for HTTP calls and SharedPrefModule for local storage
• Data → External Services: Retrofit service interfaces communicate with backend; S3 SDK for uploads; BillingManager calls Play Billing; FCM receives push; Kakao SDK for login
• App Module wires everything with Hilt (DI graph connecting modules and external services)
Architectural patterns & design principles
• Clean Architecture separation of concerns (layers depend only inward)
• MVI (Model-View-Intent) in all feature modules
• Multi-Module Gradle project for parallel build and clear boundaries
• Single source of navigation in core/navigation, feature-specific nav graphs
• Dependency Injection with Hilt modules in each core and data module