How hazemmahmoudf/taskati works
Project Type and Purpose
• This is a cross-platform Flutter application named “taskati.”
• It targets mobile (Android, iOS), desktop (Windows, macOS, Linux) and web.
• It provides task-management functionality via screens for splash, home, add-task and profile.
• Persistence is local (see lib/core/services/local).
File Structure Analysis
• Top-level platform folders: android, ios, linux, macos, windows, web.
• Flutter host entrypoints in each platform folder launch the Flutter engine.
• lib/
• core: shared services (local storage), UI utilities, theming, navigation helpers
• features: feature folders (splash, home, add_task, profile) each containing screen, model, widget code
• main.dart and taskati_app.dart wire up routing, theming and top-level app scaffold
• test/ contains widget tests.
• pubspec.yaml: dependencies for Flutter, plugins, assets.
Key README Insights
• No custom backend or external services—pure Flutter starter app.
• Encourages further Flutter development; no built-in network layer.
a. Main Components
• Platform Shells (Android/iOS/Linux/macOS/Windows/Web)
• Flutter Engine & Embedder
• Dart Application Layers:
– Presentation Layer (features/* screens & widgets)
– Core Layer (services, utils, theming, navigation)
– Data Layer (local storage via tasks_services & user_services)
b. Relationships & Interactions
• Platform Shell → Flutter Engine: initializes the engine.
• Flutter Engine → Dart App: invokes main.dart/taskati_app.dart.
• Presentation Layer → Core Layer: UI screens call core services for navigation, theming, data operations.
• Core Services (tasks_services/user_services) ↔ Local Persistence (e.g. SQLite, file storage)
c. Architectural Patterns/Principles
• Feature-based modularization: each feature folder encapsulates its UI and models.
• Layered architecture: Presentation → Core → Data.
• Unidirectional data flow: user action → UI → service → persistence → back to UI.
d. Relevant Technologies
• Flutter framework & Dart language
• Local storage plugin (e.g., sqflite or hive—see tasks_services.dart)
• Flutter widgets, theming, navigation (Navigator.push via navigator_push.dart)
Step-by-Step Guidance for the Engineer
– Presentation (features/*: splash, home, add_task, profile)
– Core (services, navigator, theme, utils)
– Data (local persistence)
3. Inside Presentation, list or iconify each screen widget.
4. Inside Core, list “tasks_services.dart,” “user_services.dart,” “navigator_push.dart,” and theme files.
6. Presentation → Core (method calls), Core → Data (read/write), Data → Core (data returns), Core → Presentation (notification/update).
9. A REST call placeholder if a future network layer is planned.