How chunhthanhde/cinema-booking works
Project type and purpose
• This is a cross‑platform mobile (and web/desktop) client application named Cinema Booking built with Flutter, following Clean Architecture + BLoC.
• Purpose: allow users to search movies, view details, auth via Firebase, book seats and time‑slots, and manage tickets.
File structure
• Top‑level “android”, “ios”, “linux”, “macos”, “windows”, “web” folders → Flutter multi‑target client.
• lib/ folder organized into layers:
• common: shared widgets, helpers, global BLoCs (authentication, theme)
• core: API provider (Dio/Retrofit), configs, constants, local storage helpers, usecase abstractions
• data: models (JSON DTOs), repository implementations, data sources (remote via Retrofit, mock, local)
• domain: entities, abstract repository interfaces, use case classes
• presentation: UI screens and feature‑specific BLoCs (login, home, movie_detail, booking, tickets, etc.)
• Configuration: service_locator.dart (GetIt DI), router.dart (GoRouter navigation), main.dart kicks off app.
README insights
• Tech stack: Firebase Auth/Firestore, Dio/Retrofit REST API, SharedPreferences, Sqflite, BLoC, Equatable, Freezed, JSON Serializable, GoRouter, YouTube Player, Google Maps, etc.
Detail level
• Layer’s major sub‑components (e.g., under Data: models, repository_impl, remote_service)
• Similar features (all booking-related BLoCs under one “Booking” container).
• Don’t overcrowd: collapse low‑level widgets into “UI Widgets” cluster but list critical ones (e.g., GoRouter, ServiceLocator).