How hellochihai/quangbadulichvietnam_dart_flutter works
Project Type and Purpose
• This is a three‐tier full-stack application:
• Backend “Server” (Node.js + Express + Mongoose)
• Admin Flutter app (multi-platform UI for administrators)
• User Flutter app (multi-platform UI for end users)
• Purpose: Promote Vietnamese tourism by serving media-rich content (videos, images), enabling user actions (search/filter, comments, favorites) and admin CRUD operations.
File Structure
• Top level: README.md, Server/, SourceCode/, data/
• Server/
• server.js – Express entry point
• models/*.js – Mongoose schemas for Admin, Customer, Province, Region
• package.json – Node dependencies (express, mongoose, cors, etc.)
• SourceCode/Admin/appadminquangbadulich/ and SourceCode/User/userappquanbadulich/
• Standard Flutter project structure: lib/, android/, ios/, web/, linux/, macos/, windows/
• lib/ organized by features, each using the BLoC pattern (bloc/, screens/, widgets/)
• pubspec.yaml – Flutter dependencies (flutter_bloc, http, video_player, youtube_player_flutter, etc.)
• data/ contains JSON files for seeding or testing.
Extract Insights from README
• Architecture:
• Frontends communicate via HTTP REST to Server
• State management in frontends via flutter_bloc (MultiBlocProvider)
• Tech stack:
• Backend: Node.js, Express, MongoDB
• Frontend: Dart/Flutter, flutter_bloc, http, video_player, youtube_player_flutter
• Key features: CRUD for comments/accounts, media playback, search/filter, favorites.
Main Components
a. Frontend Tier
• Admin Flutter App
• UI Screens (login, home, add/edit/delete attractions, user management)
• BLoC Modules per feature (e.g., addTouristAttraction_bloc)
• User Flutter App
• UI Screens (login/signup, home, detail pages, favorites, comments)
• BLoC Modules per feature (e.g., comment_bloc, touristAttraction_bloc)
b. Backend Tier
• Express Server
• API Controllers/Routes (e.g., /admin, /customer, /province, /region, /touristAttraction)
• Models (Mongoose schemas)
• Services (database access, business logic)
c. Data Tier
• MongoDB database (collections: admins, customers, provinces, regions, comments, attractions, history, culture, specialDishes)
d. External Services
• YouTube Data/API (via youtube_player_flutter)
• Video playback library in app (video_player)
Relationships and Interactions
• Admin/User Apps → HTTP(S) REST calls → Express Server → MongoDB
• BLoC Modules emit Events → UI updates on State changes
• Server uses Mongoose ORM to map schema → database collections
• External video content played via Flutter plugins (no extra server calls)
Architectural Patterns and Design Principles
• Three-tier architecture: presentation (Flutter), API (Express), persistence (MongoDB)
• Frontend: BLoC (Business Logic Component) pattern to separate UI from state & logic
• Backend: MVC-like separation (Routes → Controllers/Services → Models)
• RESTful API design: clear resource endpoints, HTTP verbs
• Configuration files: package.json, pubspec.yaml, build.gradle, etc. for build/deploy