How soen-390-w2025/soen-390 works
Project type and purpose
• This is a cross-platform mobile navigation app (“Concordia Nav”) built entirely in Flutter / Dart.
• It runs on Android and iOS, uses Google Maps + custom indoor/outdoor maps, integrates with calendar and OpenAI, and provides features such as next-class directions, POI browsing, smart planning, and accessibility settings.
File structure
• Top‐level folders:
• android/ & ios/ → platform embedding (Gradle, Xcode project, MainActivity.kt, AppDelegate.swift)
• lib/ → the Flutter app’s code, subdivided into:
– data/ (domain‐model, repositories, services)
– ui/ (views organized by feature)
– utils/ (viewmodels & helpers)
– widgets/ (reusable UI components)
– main.dart (app entrypoint)
• test/ (unit & widget tests mirroring lib/)
• .github/, .githooks/ (CI/CD + pre-commit configuration)
• Key patterns: layered separation (presentation, state, domain, data), MVVM-ish (widgets↔viewmodels↔services), repo & service layers.
README for additional insights
• Environment variables for GOOGLE_MAPS_API_KEY and OPENAI_API_KEY
• rps scripts for build/test/CI
• CI pipeline: format, lint, unit tests, Android/iOS builds, codecov upload
• Third-party libs: calendar_view, Google Maps plugin
• Labels: clear component names (e.g., “MapService,” “IndoorRoutingService,” “CampusMapView”).
• Blue rectangles for UI components
• Green rectangles for state / viewmodels
• Red clouds for external APIs