How aconinc/acon-android works
Project Type & Purpose
• Type: Android mobile application
• Purpose: A location-based “No more research” map app that allows users to sign in, onboard (preference selection), explore spots, verify local area, upload new spots, view & edit profile, and configure settings.
• Key Patterns: Single-Activity (Jetpack Navigation), Clean Architecture, MVI (Orbit), Multi-module Gradle.
High-Level Architectural Layers
Presentation (UI & State):
– App Module: Single Activity, Hilt setup, Nav graphs
– Feature Modules (signin, onboarding, spot, areaverification, upload, profile, settings):
• Composable Screens (UI)
• Orbit ViewModels (State + Side-Effects + Intents)
– Core/DesignSystem Module: shared UI components, theming
Domain (Business Logic):
– Domain Module:
• UseCases (if present)
• Repository interfaces
• Domain Models & Error types
Data (Data Delivery):
– Data Module:
• RepositoryImpls (implements Domain repos)
• Remote DataSources (Retrofit APIs)
• Local DataSources (DataStore / SharedPreferences)
• DTOs (request/response)
• Hilt Network + Auth Modules
Core Utility Modules:
– core/common (qualifiers, dispatchers)
– core/map (map utility logic)
– core/utils/feature (permissions, back-press, toast)
External Services:
– REST APIs (Auth, Onboarding, Profile, Spot, Upload, Area Verification, Map)
– Amplitude analytics
– GitHub Actions CI/CD
– Hilt DI, Retrofit/OkHttp, Coroutines/Flow, Coil image loader
Components & Relationships
• UI → ViewModel: user events trigger Orbit intents
• ViewModel → Domain → Repository interface
• RepositoryImpl → DataSource:
– If remote: Retrofit API → JSON DTO → Domain Model
– If local: DataStore → key-value storage → Domain Model
• ViewModel collects Flows from UseCases/Repositories → updates UI state
• Navigation: NavController in App Module orchestrates feature Graphs
• Shared DesignSystem: reused by all feature UIs
Architectural Patterns & Design Principles
• Single-Activity / Jetpack Navigation with nested graphs per feature
• Multi-module separation:
– core (UI components, utils)
– data (infrastructure)
– domain (pure business)
– feature (presentation + state)
• Clean-Architecture: clear dependency direction (UI → Domain → Data)
• MVI (Orbit): deterministic, unidirectional data flow
1. App Module → Feature Modules (navigation host)
2. Feature UI → Feature ViewModel
3. ViewModel → Domain (Repository interfaces / UseCases)
4. Domain → Data (RepositoryImpl)
5. Data → Remote APIs / Local DataStores
6. Feature & Data → Core Modules where applicable
– Show external services on the right: REST endpoints, Amplitude, CI
Detail Level
– Capture navigation flows between features.
– Explicitly show DI graph entry points (Application → Hilt Modules → Injected repos).
– Show state flow: UI → Intent → State → UI