How pudcheetah/mypratice_mix_3_coroutine_gson_recyclerview_intent works
Project type and purpose
• This is a single-module Android mobile application written in Kotlin.
• It demonstrates best practices for combining coroutines (for async work), Gson (for JSON parsing), RecyclerView (for list display), and Intent navigation between screens.
• Key features:
– MainActivity shows a list of items loaded from a local JSON resource.
– DetailActivity displays details for a selected item.
– Uses MVVM: MyViewModel mediates data between UI and data source.
File structure
Top-level
• build.gradle.kts, settings.gradle.kts, gradle wrapper – standard Android/Gradle config
• /app – Android application module
Under app/src/main/java/com/example/...
• MainActivity.kt – entry point with RecyclerView setup
• DetailActivity.kt – shows details of a tapped item
• MyViewModel.kt – holds LiveData/List of model objects
• MyDatabase/MyJsonClass.kt – data model class matching JSON schema
• MyDatabase/MyJsonString.json – embedded sample data
• MyRecyclerViewManager/MyAdapter.kt – RecyclerView adapter + view-holder
Under app/src/main/res
• layout/*.xml – UI layouts for list, item, and detail screens
• values, drawable, mipmap – standard resources
Tests in androidTest and test directories
README
• It contains an image only, no further textual architecture description.
• We infer architecture from source code patterns (MVVM + local data).
Elements
• Clear labels: MainActivity, DetailActivity, MyViewModel, JSON File, Adapter, Model Class
– from MainActivity to ViewModel (data request)
– from ViewModel to JSON file & back (async load)
– from ViewModel to MainActivity (LiveData update)
– from Adapter to DetailActivity (Intent navigation)
– Presentation (ViewModel) in another
– Data (JSON file, Model) in a third