How daggerpov/spawn-app-android-kotlin works
Project Type and Purpose
• This is a full-stack mobile client: an Android application written in Kotlin using Jetpack Compose and the MVVM pattern.
• It connects over HTTP to a separate REST API (“Spawn-App-Back-End”) to fetch and post event and user data. It also embeds the Mapbox SDK for map rendering.
Key Directories and Architectural Layers
• app/src/main/java/com/example/spawn_app_android/data
• model (DTOs for JSON payloads)
• remote (ApiService/ApiClient for REST calls via Retrofit or similar)
• app/src/main/java/com/example/spawn_app_android/domain
• model (business/domain objects)
• (potentially) use-case classes (not shown, but your ViewModels mediate here)
• app/src/main/java/com/example/spawn_app_android/presentation
• navigation (Compose Navigation graph)
• screens (Composables for UI)
• viewModels (UI state + calls into data/domain layers)
• app/src/main/res
External Dependencies & Services
• Spawn-App-Back-End REST API (external server)
• Mapbox SDK / Mapbox access token (external mapping service)
• Android OS and device hardware
• Build system: Gradle (Kotlin DSL)