How usmahapatra/speedalert-assignment works
Project type and purpose
• This is an Android “headless” Kotlin application (no UI) that simulates over-speed detection and alerting for a rental car system.
• It runs as a simple console-style Android app: invoke main() in Main.kt, feed speed into the system, detect violations, and issue mocked Firebase notifications.
File structure
• Top-level module app/ is a standard Android Studio Gradle module (with build.gradle.kts, AndroidManifest.xml, src/main/java, src/main/res, plus test folders).
• No frontend/backend split—this is a single APK with all logic in Kotlin classes under com.example.speedalertassign.
• Key classes under app/src/main/java/com/example/speedalertassign:
• Customer, Vehicle, RentalSession (entities)
• SpeedMonitor (service that observes speed changes)
• SpeedViolationListener (observer interface/implementation)
• FirebaseNotifier (infrastructure adapter, mocked notification)
• Main (entry-point orchestrator)
• Config files under res/xml (backup/data-extraction rules) are present but not used in logic—they represent Android resource inputs.
README for additional insights
• Confirms Kotlin + Android Studio, no UI, Firebase integration is mocked via println().
• Usage: run main() and feed values into onSpeedChanged().
Elements
• Blue for Domain entities
• Green for Service/logic
• Orange for Infra adapters
• Data flows (speed data in; alert out).