How aayushman024/project_management-frontend works
Project type and purpose
• From the file tree and README, this is a cross-platform Flutter “Project Management System” client application. It provides UI pages (login, dashboard, project detail, etc.), uses controllers for business logic, and calls out to a remote REST API to create/read/update projects, features, bugs, and teams.
File structure
• Top-level “web/” and “windows/” folders contain platform runners (HTML shell for web, C++ runner for Windows).
• lib/main.dart serves as the Flutter entry point.
• lib/pages/ holds the app’s screens (loginPage, homePage, projectDetailPage, etc.).
• lib/components/ provides reusable UI widgets (projectCard, barGraph, timeline, etc.).
• lib/controllers/ contains state‐management and business logic.
• lib/api/ defines HTTP clients and data models (apis.dart, getAllProjects.dart).
• lib/dialogBoxes/ holds pop-up forms (addBugs, addFeature, etc.).
• pubspec.yaml lists the app’s external dependencies (Flutter SDK, http package, etc.).
README for additional insights
• The README is minimal (“Project Management System”) and confirms this is purely the front-end. There is an external back-end (not in this repo) that the API module communicates with over HTTP.
Detail
• Folders under lib as separate sub-components (pages vs components vs dialogBoxes).
• Platform targets (web, windows, mobile) feeding into the same Flutter App layer.
• Explicitly call out the data model (JSON ↔ Dart classes in lib/api/models).
• Do not omit the controllers layer—this is where state management and business rules live.