How ttatta-org/ttatta_android works
Project type and purpose
• This is a Kotlin-based Android mobile application built with Jetpack Compose, organized as a multi-module MVVM architecture.
• The “app” module is the entry point; “feature/…” modules each encapsulate a screen’s UI and ViewModel; “core” holds shared domain models and repository interfaces; “data” implements those interfaces, handles network (Retrofit), preferences, and geocoding; “design” provides shared UI components and theme.
File structure
• Top-level modules:
• app – MainApplication, Hilt setup, NavHost, aggregates feature modules.
• core – domain layer (data classes, repository interfaces).
• data – data layer (Retrofit APIs, DTOs, repository implementations, DI modules, serializers, preference abstractions).
• design – UI toolkit (Composable components, character rendering, theme, assets).
• feature/… – per-feature modules (login, home, category, challenge, footprint, record, mypage); each contains its own AndroidManifest, ViewModel, Composables, DI, assets, tests.
• test/… – integration or instrumentation-test variants mirroring features.
• Gradle and Hilt modules configure dependencies and injection points.
README for additional insights
• Tech stack: Kotlin, Jetpack Compose, Navigation, Hilt, Retrofit, SharedPreference, Room, Naver Map SDK, KakaoSDK.
• Architectural pattern: multi-module, MVVM, dependency injection (Hilt).
Elements
• Clear labels: module names, components (ViewModel, Repository, API)
• Blue rectangles for UI modules (feature/design)
• Yellow for domain (core)
• Green for data layer (data module)
• Clouds for external services (REST server, Naver Map, Kakao)
Detail to capture
• Hilt injection graph: e.g., DataModule provides ServerApi, RepositoryModule binds interface→impl, PreferenceModule provides SharedPreference.
• Navigation: app/NavHost dispatching to feature NavGraphs.
• Mapping from DTOs (data/api/dto) to domain models (core/model) and back into UI state.