How kossy205/projecthub- works
Main Components
• User Interface (UI) Layer:
• This includes all the Android activities (e.g., SplashActivity, IntroActivity, SignInActivity, SignUpActivity, MainActivity, CreateBoardActivity, CardDetailsActivity, etc.) grouped under the “activities” package.
• The UI is further supported by various layouts (XML files in the res/layout directory) and view resources such as drawables and menus.
• Data Handling & Business Logic:
• The core data management is done via Firebase. In the “firebase” package, the FirestoreClass handles all Firestore-related operations while the “model” package contains data models such as Board, Card, Task, User, and SelectedMembers.
• Adapters (in the “adapters” package) and dialogs (in the “dialogs” package) mediate between the data and UI layers.
• Utility functions and constants (in the “utils” package) support the business logic.
• Asynchronous Operations and Services:
• Kotlin Coroutines facilitate asynchronous operations for better performance and battery efficiency.
• The “fcm” package includes the MyFirebaseMessagingService, which is responsible for handling Firebase Cloud Messaging, a service that interacts with external systems to push notifications.
• External Services:
• Firebase Authentication is used for user management.
• Firebase Cloud Firestore is used for data persistence and task storage.
Out the Relationships and Interactions
• The Application Startup:
• The entry point is the SplashActivity, which then directs the user to either IntroActivity or SignInActivity based on authentication.
• Authentication Flow:
• The SignInActivity and SignUpActivity handle user authentication using Firebase Auth.
• Main User Operations:
• After authentication, the MainActivity manages the list of boards/tasks.
• Navigation between screens (e.g., to create a board or view task details) is handled via intents navigating between activities.
• Data Operations:
• Each activity interacts with Firestore through the FirestoreClass to create, read, update, and delete (CRUD) operations for Boards, Cards, Tasks, etc.
• Adapters are used to populate dynamic content in lists (e.g., boards, task lists, member lists).
• Notification Flow:
• The MyFirebaseMessagingService in the fcm package listens for and handles incoming notifications, ensuring the UI is updated accordingly.