How wilson-daniel/assignment works
Main Components
• Android Application Shell:
• AndroidManifest.xml (entry point and configuration details)
• Gradle files (indicate build configurations and dependencies)
• UI Layer (View):
• Composable screens found in the "ui" package (e.g., PokemonListScreen, PokemonDetailScreen)
• Navigation component in AppNavigation.kt for routing between screens (using Navigation Compose)
• ViewModel Layer:
• The ViewModel class (PokemonViewModel.kt) that manages UI-related data.
• Model & Data Layer:
• Data Models: Classes such as Pokemon.kt, PokemonDetail.kt, PokemonList.kt, and PokemonResponse.kt representing the domain.
• Remote Data Source: RetrofitInstance.kt and PokeApiService.kt under the "remote" folder, responsible for making network calls.
• Repository: PokemonRepository.kt that abstracts data gathering (by connecting the ViewModel with the remote data source).
• External Dependencies & Libraries:
• Retrofit and Moshi for network request handling and JSON parsing.
• Coil for image loading.
• Jetpack Compose for UI components, along with Navigation Compose.
• Optionally, include data models that the repository utilizes to parse responses.
Architectural Patterns
• That the dependency management takes place at the build configuration level (build.gradle files) and the project leverages a declarative UI paradigm using composables.
• For each component, label them clearly (include file names or package names as appropriate, such as referencing MainActivity, PokemonViewModel, etc.).
• Ancillary elements such as configuration files (AndroidManifest.xml, build.gradle.kts) in a “Configuration/Build” section if needed.