How vishnu-deepan/geolocation-attendance works
Project type and purpose
• This is a full-stack, cross-platform Flutter application (“Geolocation-Based Attendance Management System”) with native Android/iOS/Web/Desktop front-ends that use Firebase backend services to authenticate users, store attendance records, and perform geolocation-based check-ins.
File structure
• Top-level “android”, “ios”, “web”, “linux”, “macos”, “windows” directories each hold platform-specific builds and native code generated by Flutter.
• The “lib” directory contains Dart code:
• lib/screens – UI pages (login, signup, home/dashboard, manual check-in, working hours, history)
• lib/service – LocationService (handles geolocation logic)
• lib/main.dart – entry point
• dataconnect & dataconnect-generated – GraphQL connector definitions and generated Dart stubs (optional data-access layer).
• Firebase config & rules files (firebase.json, firestore.rules, database.rules.json).
• Pubspec.yaml lists dependencies: firebase_core, firebase_auth, cloud_firestore (or realtime_database).
README
• Confirms use of Firebase Authentication for login/signup, Firebase Realtime Database (or Firestore) for attendance data, and native geolocation services for automatic/manual check-ins.
• Lists core features: secure auth, real-time data sync, auto/manual check-in, attendance history, working hours calculation.
Elements
• Rectangles for components (UI, services)
• Parallelograms for external APIs/plugins
• Clouds for backend services (Firebase)