How glantrox/attendance_app works
• Mobile Frontend (Android App) – This is the primary interface where teachers and students interact. It consists of various Activities (e.g., LoginActivity, RegisterActivity, DashboardActivity, AttendanceActivity, etc.), Fragments (e.g., FragmentDetailAbsen, Fragment_Check_In layout), and Adapters (e.g., AdapterAttendance, KaryawanAdapter). These can be grouped under “Presentation Layer.”
• Business Logic & Local Data Management – Represent the classes handling shared preferences, and other client-side logic (e.g., SharedPreferences.kt), along with helper classes in the “model” package that define data structures for Attendance, Login responses, etc.
• External Backend Services – Represent Supabase as the primary backend API component. Also include external integrations like the Imgur API which is used for uploading attendance and profile pictures.
Relationships and Interactions
• Mobile UI Components communicate directly with the Business Logic layer.
• Business Logic uses Model classes and interacts with the Data Access layer to fetch or update attendance data.
• The Data Access layer, via the SupabaseApi, communicates with the Supabase server component.
Architectural Patterns and Design Principles
• The file structure suggests a separation of concerns, potentially following an MVP/MVVM pattern. Emphasize the separation between UI (Activities/Fragments), business logic, and data access.
• Mention modularization – the clear division between presentation (UI and layouts), domain (logic and models), and data (API handling) layers.
• Marking external dependencies (Supabase and Imgur) separately.
Relevant Technologies, Frameworks, and Libraries
• Kotlin as the programming language.
• Android Studio’s platform-specific components (Activities, Fragments, Adapters).
• Supabase API for backend services.
• Imgur API for managing attendance images.
• Gradle for build automation.
• Google services (notice the google-services.json file) which also indicates integration with Firebase/Google APIs for additional functionalities.