How noumanzindani/traveller works
Project type and purpose
• Traveller is a cross-platform Flutter mobile/desktop/web client app for browsing and booking trips.
• It uses MVVM (Model-View-ViewModel) with Provider for state management.
File structure
• Top-level folders: android, ios, linux, macos, windows, web → platform targets via the Flutter engine
• lib/
• model/ – Dart classes representing Trip data
• provider/ – ViewModel/state classes (e.g., Favor)
• view/ – Screens (Splash, Home, Detail, Recipet)
• widgets/ – Reusable UI components (Slider, ScreenTitle, TripList)
• main.dart – App entry point, sets up DI and routes
• pubspec.yaml + pubspec.lock – dependencies (provider, slide_to_act, uuid, flutter_native_splash)
• README.md – confirms MVVM architecture, feature set, tech stack
README for additional insights
• Architecture: MVVM
• Packages:
• provider – state injection & change notifications
• slide_to_act – custom UI control for booking
• uuid – generate unique IDs
• flutter_native_splash – splash screen
Components
a. Presentation Layer
• Views (SplashView, HomeView, DetailView, RecipetView)
• Widgets (TripList, ScreenTitle, Slider, RecipitText)
b. State & Business Logic
• ViewModels/Providers (Favor, plus any you add for tripListing, booking)
c. Data Layer
• Models (Trip, User, Booking – represented by trip.dart and future classes)
d. External Systems
• REST API endpoints (destination catalogue, booking service)
• Third-party packages (uuid, slide_to_act)
e. Platform Integration
• Flutter Engine
• Platform channels if any native code (android/app, ios/Runner)
Relationships & interactions
• Views subscribe to ViewModels via Provider → receive state & commands
• ViewModels call Services to fetch/update data → map JSON to Models
• Models represent domain data and flow back into ViewModels → trigger UI updates
• External API ↔ Services → JSON ↔ Models
• Platform layer handles rendering, plugin callbacks, native integrations
Architectural patterns
• MVVM: strict separation of UI (Views), state/logic (ViewModels), and data (Models/Services)
• Dependency injection & reactivity via Provider
• Single source of truth: ViewModel state drives entire UI
Detail orientation
• Don’t over-complicate: focus on MVVM layers, data flow, and major dependencies
• Component is named exactly as in the codebase (e.g., FavorProvider, Trip model)