How kbdevs12/cahaya-futsal-frontend works
This is a Flutter application whose feature structure suggests field availability and booking, with authentication, payment, bookings, notifications, and profile capabilities. The README is only a Flutter starter template, and the sampled source contains platform launchers rather than Dart feature code; therefore, the product workflow is inferred from the file tree, and internal feature wiring is not asserted.
Main entry points: router.dart Navigation · main.dart Flutter entry · app.dart App shell · availability Field availability
Components 17
App shell
- Flutter entry
lib/main.dart - App shell
lib/src/app/app.dart - Navigation
lib/src/app/router.dart - Home
lib/src/features/home
Booking journey
- Field availability
lib/src/features/availability - Create booking
lib/src/features/availability/presentation/screens/create_booking_screen.dart - My bookings
lib/src/features/bookings - Payment QR
lib/src/features/payments
Account
- Authentication
lib/src/features/auth - User profile
lib/src/features/profile - Notifications
lib/src/features/notifications
Shared services
- HTTP client
lib/src/core/network/dio_client.dart - Token storage
lib/src/core/storage/token_storage.dart - Push messaging
lib/src/core/notifications/fcm_service.dart
Other components
- User
- Backend API
- Firebase
Connections 11
- User → Flutter entry: launches
- Flutter entry → App shell: starts
- App shell → Navigation: uses navigation
- Navigation → Authentication: routes
- Navigation → Home: routes
- Navigation → Field availability: routes
- Navigation → My bookings: routes
- Navigation → Payment QR: routes
- Navigation → User profile: routes
- Navigation → Notifications: routes
- Field availability → Create booking: offers booking