How chayan9991/service_booking_flutter_app works
Project type and purpose
• This is a cross-platform (Android, iOS, Web, macOS, Windows) Flutter client application for service booking, built with Clean Architecture.
• Core features include user authentication (Firebase Email/Password), service browsing and booking, and planned payment integration (Razorpay/Stripe) and admin panel.
File structure
• Top-level folders (android, ios, web, macos, windows) host platform-specific Flutter runners.
• The lib/ directory is organized by Clean Architecture layers:
– core/: utilities, themes, routing, DI setup
– data/: models, repositories (auth, etc.)
– logic/ or domain/: business services/use cases
– presentation/: UI screens, widgets, Bloc/Cubit state managers
• Configuration files: pubspec.yaml, firebase.json, flutterfire and build scripts under each platform.
README for additional insights
• Confirms Clean Architecture, dependency injection (get_it), state management (Cubit), and Firebase integration.
• Points to future modules: payment service, admin panel.
Detailed capture of architectural essentials
• Service Locator (get_it) injecting AuthRepositoryImpl into AuthCubit
• Data flow from LoginScreen → AuthCubit → AuthUseCase → AuthRepository → Firebase Auth
• Error-handling or state transitions in the Bloc/Cubit flow