How kbm90/drivio works
Project Type and Purpose
• This is a cross-platform Flutter mobile application (“drivio”) implementing a ride-sharing service with two primary user roles: Drivers and Passengers.
• It leverages Flutter’s single codebase to produce Android and iOS clients (see android/ and ios/ folders), and implements modular Dart code under lib/ for authentication, shared/common logic, driver-specific flows, and passenger-specific flows.
File Structure Analysis
• Top-level:
• android/ and ios/ – native build configurations and entry points for each platform.
• lib/ – the entire Dart codebase, subdivided into:
– auth/: login & registration screens.
– common/: shared constants, helpers, models, providers (ChangeNotifiers), services (HTTP/REST clients), and widgets.
– driver/: driver-specific models, state providers, services (ride requests, notifications, map reports), UI screens, modals, and widgets.
– passenger/: passenger-specific screens, widgets, models.
– main.dart: app entry, routing, and high-level UI shell.
• Notice the use of the Provider pattern for state management (lib/.../providers) and a clear separation of concerns: UI → Providers (business logic) → Services (API calls) → Models (data).
Key Architectural Insights from the README
• The README is boilerplate but confirms this is a Flutter project and implies standard Flutter build/deploy workflows.