How muhammadmannan/css-496-capstone works
Project Type and Purpose
• This is a Flutter‐based, cross-platform client application (“campus_connect”) targeting Android, iOS, web, macOS, Windows, and Linux.
• It presents a series of UI pages for club discovery, club profiles, posts, student home, and authentication, with the expectation that it will call out to one or more back‐end services (e.g. REST APIs, Firebase).
File Structure
• Top-level platform folders (android/, ios/, macos/, linux/, windows/, web/): each contains the native runner, plugin registrant, build configurations, and native resources.
• lib/: contains main.dart (entry point) and pages/ (one Dart file per screen).
• pubspec.yaml / pubspec.lock: lists dependencies (Flutter SDK, plugins, etc.).
• test/: contains widget tests.
README
• Boilerplate Flutter README—no built-in back-end included, but clearly intended as a starting point for a full Flutter app.
Main Components
A. Platform Runners
• Android, iOS, Web, macOS, Windows, Linux “Runner” projects.
• Each invokes the Flutter Engine and registers platform plugins.
B. Flutter Engine & Embedder
• Shared native library that hosts Dart VM and renders via Skia.
C. Dart Application
1. Entry Point (main.dart)
2. Presentation Layer (Widgets in lib/pages/*.dart)
3. Business Logic / State Management (e.g. BLoC, Provider—insert your chosen pattern here)
4. Data Layer (API clients, local persistence)
D. External Services
• Authentication service (e.g. Firebase Auth or custom OAuth)
• Data APIs (e.g. REST/GraphQL endpoints, Firestore)
• Optional local cache or SQLite
Relationships & Data Flows
• User taps UI → Presentation Layer
→ Business Logic (validates, triggers events)
→ Data Layer (performs HTTP/GraphQL/DB calls)
→ External Service
→ returns data → Data Layer → Business Logic → Presentation → renders updated UI
• Platform Runner ↔ Flutter Engine ↔ Dart App (bidirectional for platform channel calls, e.g. pushing notifications, permissions).
Architectural Patterns & Design Principles
• Layered Architecture (Presentation / Domain / Data).
• Separation of Concerns via State Management (e.g. BLoC or MVVM).
• Single codebase reused across all platforms.
• Plugin architecture for native feature access.