How otniel113/rentacar-mobile works
Project type and purpose
• This is a cross-platform Flutter mobile application (“Rent A Car Mobile”) whose purpose is to let members browse vehicles (minibus, big car, small car), view details, register/login/logout, manage their profile, and make/view bookings.
• The backend (not included here) exposes REST APIs for authentication, profile, vehicle listings, and bookings.
File structure
• Top-level platform folders (android/, ios/, web/, windows/) contain the platform runners generated by Flutter.
• lib/ contains the core Dart application, organized into:
– api/: service classes calling REST endpoints
– models/: domain objects (Booking, Member, Minibus, Mobilbesar, Mobilkecil)
– session/: SessionManager (token storage & retrieval)
– utils/: input validators
– views/: UI layers split by BottomNavBar modules (home, booking, profile) plus login.dart, regist.dart, home.dart
• Configuration files include pubspec.yaml, analysis_options.yaml, and platform build scripts.
README for additional insights
• The README confirms four main UI modules mapped to BottomNavBar tabs: Home, Login/Register/Logout, Profile, Booking.
• The mobile app is a client for members; an admin web app (separate repo) manages vehicle availability.
Detailed capturing of essential architecture
• BottomNavBar modules as separate UI components that share the same API and SessionManager.
• External dependencies (e.g., pubspec plugins) if they play a critical role (secure storage, http).