How ejeonghun/universus_flutter works
Main Components
• Client/Fron-tend (Flutter App):
– Includes platform-specific parts (android, ios, macos, linux, windows, web directories)
– Contains the Flutter “lib” folder that is organized by feature (auth, community, chat, club, main page, versus, etc.)
• API Communication Layer:
– You have custom API call utilities (see lib/class/api/ApiCall.dart and DioApiCall.dart) that handle network requests.
• Back-end Service (External):
– Although not part of this repository, the README informs you of a Spring Boot back-end, running on Apache Tomcat and containerized via Docker.
• External Services and Integrations:
– Firebase (firebase_options.dart for FCM push notifications and other Firebase services)
– Third-party authentication (Kakao and university email verification)
– Google Maps integration (via shared/GoogleMap.dart), and possibly payment processing and notification click handling.
• Data Models & Business Logic:
– Encapsulated in various “_Model.dart” files. These are closely tied to UI components (the “_Widget.dart” files), following a design pattern that separates UI from data and logic.
Relationships and Interactions
• UI Components (Widgets) communicate with their corresponding Models to fetch, display, and update data.
• Both UI and Models use the API call components to exchange data with the back-end server.
• User actions (e.g., log in, send chat messages, create clubs or sports matches) trigger API calls.
• Third-party services are called when needed (e.g., Firebase for push notifications, and Google Maps for location data).
• The back-end services handle data persistence (using Oracle DB as per the technology stack), business logic, and serve the RESTful APIs.
Architectural Patterns and Design Principles
• Modular Separation:
– The project is broken down into clear feature areas (auth, chat, club, community, versus, etc.), making it easy to map each module as a separate component.
• MVVM/MVC-like Structure within Flutter:
– Models for data, UI widgets for presentation, and clear separation between API communications.
• Multi-platform Support:
– Distinct directories for platform-specific implementations suggest cross-platform support using Flutter’s unified development approach.
• Use of External Integrations:
– Integration with Firebase, Google Maps, and secure local storage (for user credentials) provide enhanced performance and functionality.
Specific Technologies & Frameworks
• Front-end: Flutter (Dart), using Flutter-specific frameworks for custom widgets, themes, and utility functions.
• Back-end: Java with Spring Boot, Docker, Apache Tomcat.
• Communication: HTTP/REST APIs handled by Dio in Flutter.
• External: Firebase, Google Maps, Payment gateways (as seen in shared/payment.dart), and others mentioned in the README.