How team-wable/wable-android works
Project Type and Purpose
• Wable is an Android full-stack mobile application, built in Kotlin with Jetpack Compose.
• It provides a community platform for supporting teams and players without harassment, featuring login, feed, news, notifications, profile, posting, and “view-it” functionalities.
• It follows official Android architecture guidance and a modularization strategy: a single “app” runner module, multiple feature modules, and shared “core” libraries.
File-Structure Analysis
• Top-Level Modules
• app: the Android application entry, Gradle config, manifest, Proguard, Firebase messaging service.
• build-logic: custom Gradle convention plugins (AndroidApplicationPlugin, HiltPlugin, RetrofitPlugin, etc.) and version catalog.
• core/**: shared libraries:
– common: MVVM base classes, DI qualifiers, utilities, resources
– data: repository interfaces, mappers, implementations, ContentResolver utils
– datastore: local Preferences DataStore module
– designsystem: reusable UI components and theme definitions
– domain: pure business-logic use cases (unit tested)
– model: data classes shared across layers
– navigation: NavHost graph types and helpers
– network: Retrofit services, interceptors, DTOs, paging source
– ui: base fragments, UI components, adapters, navigation ext
• feature/**: feature-specific modules for auth, community, home, main-compose, main, news, notification, onboarding, posting, profile, viewit.
• config files: settings.gradle.kts, libs.versions.toml, project.dot (for dependency graph), CI workflows.
README Insights
• Architecture: MVVM + Clean Architecture.
• Modularization: clear boundary between “app,” “feature” modules, and “core” libraries.
• Tech stack: Hilt for DI, Retrofit + Coroutines/Flow for networking, DataStore for caching, Jetpack Compose + Navigation + Paging + Material 3 for UI, custom Gradle conventions.
a. Main Components
• App Module: AndroidApplication, FirebaseMessagingService, DI entry point (Hilt).
• Feature Modules (Auth, Community, Home, News, Notification, Posting, Profile, ViewIt, Onboarding, MainCompose, Main)
• Core Libraries:
• UI & DesignSystem (Compose components, theme)
• Navigation (NavHost graphs)
• Domain (UseCases)
• Data (Repositories, Mappers)
• Network (Retrofit services, DTOs)
• Datastore (Preferences)
• Common (Base classes, utilities)
• External Services: REST API endpoints, Firebase Cloud Messaging, local DataStore
b. Relationships & Data Flow
• Features request data via Domain use cases → Data layer (Repository interface) → Network or Datastore
• Network calls made via Retrofit services → parsed into DTOs → mapped to domain/model classes
• Datastore (DataStoreModule) provides local key-value storage for prefs
• DI (Hilt) injects modules into features and core
• UI (Compose or Fragments) binds to ViewModel (inherits BaseViewModel) and observes StateFlow for states and side effects
• Navigation graphs orchestrate fragment/compose screen transitions
• FirebaseMessagingService receives push messages and routes into the app
c. Architectural Patterns
• Clean Architecture layers (UI → Domain → Data → Network / Datastore)
• MVVM with StateFlow & SideEffect pattern
• Feature Modules encapsulate UI + ViewModel + Navigation + DI bindings
• Shared Core modules enforce consistency and avoid duplication
• Custom Gradle convention plugins ensure uniform build settings
d. Key Technologies & Frameworks
• Jetpack Compose & Navigation
• Retrofit + Kotlin Coroutines / Flow
• DataStore (Preferences)
• Hilt for DI
• Paging 3 for list pagination
• Material 3 design system
• JsoupParser for HTML parsing in Data layer
• Custom Gradle Version Catalog + Convention Plugins