How reemakusa/staypal works
Project Type and Purpose
• StayPal is a multi-platform (iOS, Android, web, desktop) Flutter application for booking hotels and events, with user, admin, hotel-manager, and event-organizer roles.
• It uses Firebase for authentication, data storage (Firestore), cloud functions, and hosting.
File Structure Analysis
• Top-level “android”, “ios”, “linux”, “macos”, “windows”, “web”: Flutter platform shells.
• “functions/”: Firebase Cloud Functions (Node.js).
• “lib/”: core Dart code, organized by feature:
• DB + firebase_options.dart
• constants, utils, theme
• models (POJOs for bookings, events, hotels, user, etc.)
• services (booking_service, user_service, event_service…)
• screens (split into sub-folders by feature/role: auth, homePage, booking, detailsPage, admin, event_organizer, hotel_manager, profile, wishlist, reviews, searchResult)
• viewmodels under each screen (MVVM pattern).
• widgets (reusable UI components and webNavBar).
• Firebase config files: .firebaserc, firebase.json, google-services.json, GoogleService-Info.plist.
Key Architectural Insights from README
• Although the README is boilerplate, the presence of Firebase config + Cloud Functions implies a serverless backend with user- and role-based workflows.