How dillibasker/jec_app works
Main components
• Flutter Frontend: This module is multi-platform (Android, iOS, Web, Windows, macOS, Linux) and includes various pages like login, homepage, attendence page, assignment page, exam timetable, etc.
• Node.js Backend: This module provides RESTful API endpoints, as seen in its directory structure with routes for “Attendence” (adding students, fetching records, marking attendance), “auth” (login, register, forgot/reset password, Google auth), and “profile” (user profile management with an auth middleware).
• Database (Implied): Although not explicitly shown in the file structure, the existence of models (Department, students, userSchema) suggests that there is a database layer that the Node backend interacts with.
• External Services: Depending on the authentication routes (such as Google auth) and potential integrations (like email for password resets), there may be external APIs or services involved.
Architectural patterns and design principles
• Separation of Concerns: The clear split between the frontend and backend shows adherence to this pattern.
• REST API Design: The Node backend’s route structure suggests a clean RESTful architecture.
• Cross-Platform Design: The Flutter frontend is designed to work across multiple operating systems, which is an important design nuance.
• Middleware/Authentication: The “authMiddleware” in the profile routes signals the use of middleware for authentication/authorization.
Relevant technologies and frameworks
• Frontend: Flutter (Dart) framework for mobile and multi-platform applications.
• Backend: Node.js, with Express.js (inferred from route structure) for routing and API handling.
• Authentication/External APIs: Google authentication and password recovery methods imply integration with external identity providers.