How google-developer-training/basic-android-kotlin-compose-training-race-tracker works
Main Components
• UI Layer – This includes the activities and UI components built using Jetpack Compose (although some parts may use traditional XML-based resources as well). Highlight components such as MainActivity.kt and the UI theme files.
• Coroutine Handling – Emphasize the use of Kotlin coroutines for asynchronous operations that drive the simulation or UI updates.
• Resource Management – Include a layer for resources and assets (images, dimensions, strings) which are found in the app/src/main/res directories.
• Testing – Note the test components (e.g., RaceParticipantTest.kt) that verify the logic.
Relationships and Interactions
• That the Android UI (the Activity and Compose components) interacts with the business logic.
• From user input (via UI buttons) → activity which then triggers coroutine-based logic.
• Data flow from the logic layer back to UI updates.
• Separate the concerns by drawing clear boundaries between UI, logic, and resources.
Architectural Patterns and Design Principles
• As a sample app, the architecture is relatively simple, but still consider illustrating a separation of concerns.
• The UI components (like MainActivity) directly permit interactions that then trigger asynchronous operations handled by coroutines — this separation can be flagged.
Technologies and Tools
• Kotlin and Jetpack Compose – underline that the UI is likely built using Compose (given the pre-requisites in the README).
• Gradle – show the build system (files like build.gradle.kts, settings.gradle.kts).
• Optional: mention testing frameworks if any (from testing files).