How mohamedcs1/poke works
Project type and purpose
• This is an Android mobile application (“Poke”) written in Kotlin.
• Its primary function is to fetch a list of Pokémon from a remote API, display them in a RecyclerView, and allow the user to save favorites locally.
File structure
Top-level “app” module
• build.gradle / AndroidManifest.xml / proguard-rules: standard Android config
• src/main/java/com/example: contains the core code, organized into:
– poke: Application class, Activities (MainActivity, FavActivity)
– viewmodels: MVVM ViewModels (PokemonsViewModel)
– repository: Repository layer that exposes data to ViewModels
– network: Retrofit interface (PokemonApiService)
– database: Room DAO and Database classes (PokemonDao, PokemonDataBase)
– di: Dependency-injection modules (RetrofitModule, DataBaseModule)
– pojo: Data models (Pokemon, PokemonResponse)
– Adapters: RecyclerView Adapters for list and favorites
– Tools: Converter utilities for Room type conversions
• src/androidTest & src/test: Instrumentation & unit tests
README
• Minimal content (“# Poke”), but combined with code it confirms it’s a client-only MVVM Android app using Retrofit + Room + DI.