How rhkrskdud/team_project1 works
Project type and purpose
• This is a cross-platform Flutter mobile (and desktop/web) application named “스마트환승철” (Smart Subway), whose purpose is to compute and display optimal subway routes (minimum distance/time), allow station search, favorites, plus mini-games and auxiliary features (dark mode, language toggle). It uses Firebase as its backend (for data persistence) and is built/deployed to Android, iOS, Web, Windows, Linux, and macOS targets.
Key architectural components
a. Client Application (Flutter)
– UI Layer: Flutter widgets under lib/widgets, screens under modules (FindWay, SearchSta, Setting, killingTime).
– Domain/Business Logic Layer:
· Route-finding algorithms (lib/FIndWay – graph construction, Dijkstra for distance/time).
· Mini-game logic (lib/killingTime).
· Settings logic (dark mode, language switching in lib/Setting).
– Data Layer:
· Firebase integration (lib/firebase_options.dart, lib/util/firebaseUtil.dart) for persisting favorites and user preferences.
· Local assets (images under assets/images, translations under assets/langs).
b. External Service
– Firebase (Firestore or Realtime Database) for storing user-specific data (favorites, maybe user settings).
– Google-services (android/app/google-services.json, iOS equivalent).
c. Build & Deployment Targets
– Flutter toolchain (pubspec.yaml, platform directories: android/, ios/, web/, windows/, macos/, linux/).
Relationships & Data Flow
– UI Layer ↔ Business Logic: user taps UI widgets → Business services are invoked (search route, play game, toggle settings) → UI updates.
– Business Logic ↔ Data Layer: services call Firebase SDK (through firebaseUtil) to read/write user data.
– Asset Loading: UI and logic layers load JSON/graph data & images from bundled assets.
Architectural Patterns & Principles
– Layered architecture: clear separation between Presentation (widgets), Domain (route/search logic), Data (Firebase & assets).
– Modular code organization: each feature in its own directory (FindWay, SearchSta, Setting, killingTime).
– Single codebase, multiple platform outputs via Flutter’s cross-compilation.
– BaaS (Backend-as-a-Service) approach—no custom server code, all persistence via Firebase.