How ibtihalba/productcatalog works
Project type and purpose
• This is a native Android mobile application named “ProductCatalog.”
• Its primary purpose is to display a list of products, allow updates via dialogs, and run unit/instrumentation tests.
File structure
• Top-level Gradle files (build.gradle, settings.gradle, gradle.properties, gradlew): define project build and dependencies.
• app/ module: the Android application.
– src/main/java/mgarzon/createbest/productcatalog: contains MainActivity, domain models (Product, ProductList).
– src/androidTest: UI/instrumentation tests.
– src/test: local unit tests.
– google-services.json, proguard-rules.pro: config for Firebase services and release builds.
• .circleci/config.yml: handles CI pipeline.
• .gitignore, .gitattributes, IDE files: development metadata.
README
• Minimal content; shows CircleCI build badge.
Detailed breakdown
– Branch into two lanes: UI Lane (MainActivity → Layout XMLs → RecyclerView) and Data Lane (ProductList ↔ Product).
– At the bottom, show “CircleCI” pulling from GitHub, invoking Gradle tasks (assembleDebug, test, connectedAndroidTest).