How pess0a/android-certification-study works
Project type and purpose
• This is a native Android mobile application whose sole purpose is to help developers prepare for the Google Associate Android Developer Certification.
• It covers five study topics (Android core, UI, data management, debugging, testing) by grouping content, sample code, and interactive exercises into topic-specific screens.
File structure
• Provided file tree only shows .gitignore and README.md, which implies a standard Android Studio project layout underneath (an app/ module with src/main/java, src/main/res, plus src/androidTest and src/test).
• Expect Gradle build files (build.gradle), Android manifest, resource folders, and default configuration files.
• No microservices or external back-ends—this is a single APK.
README for additional insights
• The README lists the five major certification topics (A–E) with sub-bullets describing required knowledge and features.
• There’s no mention of external APIs, cloud services, or server components— everything runs locally on the device.
Main components
a. Presentation Layer
– Activities or Fragments per topic (A, B, C, D, E)
– Custom Views (e.g., ConstraintLayout screens, RecyclerViews with Paging)
– Navigation components (menu, drawer navigation)
b. Domain / ViewModel Layer
– ViewModels exposing LiveData to the UI
– Use-case or controller classes handling business logic (e.g., schedule a JobScheduler task)
c. Data Layer
– Room database (Entities + DAOs)
– Repository that mediates between DAOs and ViewModels
– SharedPreferences or DataStore for user preferences
– Raw resources/assets parser for static study content
d. Android OS & Services
– JobScheduler / WorkManager for background tasks (e.g., reminders)
– NotificationManager for outside-UI messages
– System Log for debugging output
e. Testing Modules
– Local unit tests (src/test/java) using JUnit
– Instrumentation tests (src/androidTest/java) using Espresso
Relationships and interactions
• UI components observe LiveData from ViewModels → ViewModels call Repository APIs → Repository interacts with Room DAOs or assets
• When the user schedules a background task, ViewModel triggers JobScheduler → Android OS invokes a Worker → Worker posts a notification via NotificationManager
• Debug flow: developers drop breakpoints in Activities/ViewModels/DAOs → use System Log for trace statements
• Testing: unit tests target ViewModels and Repository logic; Espresso tests simulate UI flows through Activities/RecyclerViews
Architectural patterns and design principles
• MVVM (Model-View-ViewModel) with a clear separation of concerns
• Repository pattern to abstract data sources (Room, assets, preferences)
• Single-Activity or multi-Activity navigation using the Android Jetpack Navigation components
• Use of LiveData and Paging library for reactive UI updates
• Dependency Injection (optional) to decouple ViewModels from Repositories (e.g., Dagger/Hilt)