How aliza02/taskmanager works
Project Type and Purpose
• This is a cross-platform (Android, iOS, Web, macOS, Windows, Linux) Flutter application called “Taskmanager.”
• It provides project collaboration, task tracking, comments, and notifications (push and email).
• Uses Firebase (Auth, Firestore, Cloud Messaging), EmailJS API for emails, BLoC for state management, and dependency injection.
File-Structure Highlights
• Top-level: platform folders (android, ios, macos, windows, linux, web), standard Flutter host code.
• lib/: the core app code, organized into:
• main.dart (app entry)
• routes/: navigation definitions and page mappings
• screens/: UI pages grouped by feature (auth, home, workspaces, comments, notifications)
• widgets/: reusable UI components
• bloc/: BLoC classes (events, states, blocs) per feature (tasks, projects, members, user, navigation)
• controllers/: “use-case” or service layer classes (project_controller, etc.)
• data/: data‐access layer (Firebase auth, database functions, email sending)
• notification/: local notification wrappers
• injection/: DI setup for controllers and services
• pubspec.yaml: dependency list (flutter, firebase, bloc, get_it or injectable, etc.)
Architecture Synopsis from README
• UI screens use BLoC to manage state.
• BLoC delegates to controllers/use-cases.
• Controllers call data layer (database functions or email sending).
• Data layer interacts with Firebase services and EmailJS API.
• Notifications: uses Firebase Cloud Messaging + local notifications wrapper.
Components
a. Frontend (Flutter App)
• Platform Hosts (Android, iOS, Web, Desktop)
• UI Layer (screens, widgets)
• Navigation/Routes
b. State Management Layer
c. Domain/Service Layer
• Controllers (project_controller, etc.)
d. Data Layer/Repositories
• Firebase Auth & Firestore Database Functions
• EmailJS Service
• Local Notification Service
e. Dependency Injection
• DI Container (provides controllers, repositories to BLoCs)
f. External Services
• Firebase Cloud Messaging
• EmailJS API
• Firebase (Google) Sign-in
Relationships & Data Flows
1. UI → BLoC (dispatch events, read states)
2. BLoC → Controllers (invoke use-cases)
3. Controllers → Data Layer (perform CRUD, send email)
4. Data Layer ↔ Firebase services (Auth, Firestore, FCM)
5. Data Layer → EmailJS (REST call)
6. FCM → Notification Service → UI (push notifications)
• DI container injects controllers and repos into BLoCs at startup.
Architectural Patterns & Principles
• Separation of Concerns: UI vs. state vs. domain vs. data
• BLoC Pattern for reactive state management
• Dependency Injection (get_it/injectable) for decoupling
• Repository pattern over Firebase services
• REST integration for EmailJS alongside real-time DB