How ibtasam-98/trippy-go works
Project type and purpose
• TrippyGo is a cross-platform mobile and web application built with Flutter. Its primary purpose is to enable travel planning and booking, with separate feature sets for administrators (user and accommodation management) and end-users (search, booking, review).
File structure
• Top-level “android”, “ios”, “linux”, “macos”, “windows”, “web” folders: platform embedding for Flutter.
• “lib/app” subdivided into:
• config (theme, sizing)
• controllers (business logic, per screen, split by admin and user)
• views (UI pages, split by admin, auth, user)
• widgets (reusable components)
• “firebase.json” and “firebase_options.dart”: integration with Firebase services (Auth, Firestore, Storage).
• pubspec.yaml: Flutter dependencies (likely firebase_auth, cloud_firestore, getx or provider).
• build scripts and manifests under each platform.
README for additional insights
• Confirms feature sets: admin (user & accommodation CRUD), user (booking CRUD, search, reviews).
• No on-prem backend folder, implying reliance on Firebase or a managed backend.
Detailed steps for the engineer
2. Inside the client block, subdivide into three horizontal layers: UI (top), Controllers (middle), Services (bottom).
3. On the right, place Firebase services grouped (Auth, Firestore DB, Storage).
– UI → Controllers
– Controllers → Services
– Services ↔ Firebase (data flow)