How blastblastblast/soar works
Project type and purpose
• SOAR is a native Android full-stack application (mobile client) whose goal is to help small-scale rocketry teams by:
• Managing launch sites on a Mapbox map
• Fetching and evaluating MET weather data (Locationforecast, GRIB2, Sunrise/Sunset)
• Simulating 3D rocket flight trajectories based on user-configured parameters
File structure
• Single Gradle “app” module containing:
• src/main/java/no/uio/ifi/in2000/met2025/data ⇒ data layer
– local/… (Room database, DAOs, preferences, repositories)
– remote/… (Ktor HTTP sources & repositories)
– models/… (API & domain models)
• src/main/java/no/uio/ifi/in2000/met2025/domain ⇒ domain layer
– business logic (interpolators, trajectory calc, weather model)
• src/main/java/no/uio/ifi/in2000/met2025/di ⇒ Hilt modules for dependency injection
• src/main/java/no/uio/ifi/in2000/met2025/ui ⇒ UI layer
– common components, navigation, Compose screens & view models
• assets (3D .glb models), res (Drawables, layout values, Mapbox token)
• Gradle scripts (build.gradle.kts, settings.gradle.kts), KSP annotation processing, Hilt, Ktor, Room
README for technical stack
• Kotlin + Jetpack Compose (UI)
• Dagger-Hilt (DI)
• Ktor HTTP client (networking)
• Mapbox Android SDK + Turf (map & geospatial tools)
• Room (local DB)
• Coil (image loading)
• External APIs: MET Locationforecast, GRIB2, Sunrise/Sunset
Components
a. Main components
• UI Layer (Jetpack Compose screens & ViewModels)
• Domain Layer (Interpolate, calculate trajectories, weather evaluation)
• Data Layer
– Local Data Source (Room database + UserPreferences)
– Remote Data Source (Ktor clients to MET APIs)
• Dependency Injection Container (Hilt)
• External Services
– MET Locationforecast API
– MET Isobaric GRIB2 API
– MET Sunrise/Sunset API
– Mapbox SDK (Map & Turf)
• Assets (3D rocket models .glb)
b. Relationships & interactions
• UI → ViewModel (state + events)
• ViewModel → Domain use-cases (injected via Hilt)
• Domain → Repository interfaces
• Repositories → LocalDataSource (Room) OR RemoteDataSource (Ktor)
• RemoteDataSource ↔ External MET APIs
• UI ↔ Mapbox SDK (through injected Mapbox client)
• DI container wires all dependencies
• Assets loaded by UI (3D viewer component)
c. Architectural patterns
• MVVM (UI ↔ ViewModel ↔ Domain)
• Clean separation: UI / Domain / Data
• Repository pattern (abstract data sources)
• Dependency Injection (Hilt modules)
d. Key technologies
• Jetpack Compose, ViewModel, LiveData/StateFlow
• Room (Database, DAO)
• Ktor (HTTP client)
• Mapbox Android SDK + Turf
• Dagger-Hilt (AppModule)
Essential elements
• Component names (UI screens, ViewModels, use-cases, repositories, data sources)
• External service endpoints and SDKs