How team-mument/mument-aos works
Project type and purpose
• This is a multi-module Android mobile application (“MUMENT”) built with a Clean-Architecture flavor: MVVM + MVI.
• It’s a client-side app for recording and viewing music impressions, with features like social login, home feed, detail screens, record creation, notifications, and more.
File structure
Top-level modules:
• app: the Android application entry point, Dagger-Hilt setup, launcher Activity, AndroidManifest, and glue to feature modules.
• feature/*: six UI feature modules (detail, home, locker, login, mypage, record), each encapsulating its own Activities/Fragments, ViewModels, and layouts.
• navigation: abstraction for in-app navigation (navigator providers).
• data: data layer (controllers, datasources, DTOs, Room DB, Retrofit services, mappers, repositories).
• domain: domain layer (entities, repository interfaces, use-cases).
• core & core_dependent: shared base classes, utilities, common UI widgets & extensions.
• buildSrc: centralized Gradle dependency management.
README for additional insights
• Architecture: MVVM + MVI, Clean layers.
• Libraries: Jetpack, Navigation, Lifecycle, Hilt, Coroutine, Retrofit/OkHttp, Timber, Firebase FCM, Lottie, Coil, Kakao SDK.
Detail
• Hilt modules (NetworkModule, RepositoryModule, UseCaseModule, RoomModule, etc.) under App module to show DI bindings.
• Feature modules individually to reflect multi-module boundaries.
• Core and core_dependent as shared libraries consumed by both Presentation and Data layers.