ramonsantospinto/uberclone

Purpose and Entry Points

UberClone is a Flutter Android/iOS urban-mobility portfolio app centered on location, destination search, route display, and trip lifecycle state. Flutter starts at lib/main.dart; native hosts bootstrap the Flutter runtime through android/app/src/main/kotlin/br/com/uberclone/uberclone/MainActivity.kt and ios/Runner/AppDelegate.swift.

Composition and Dependency Boundary

Centralized GetIt registration wires presentation to domain contracts and concrete data services in lib/core/DI/injection.dart. This is the main substitution boundary: UI/Bloc code should consume service interfaces rather than Google/Dio implementations. Shared device-location access sits separately in lib/core/services/location_service.dart.

Map Feature Structure

The primary feature is isolated under lib/features/map. Its domain layer defines provider-agnostic contracts and trip state: lib/features/map/domain/services/i_places_service.dart, lib/features/map/domain/services/i_directions_service.dart, and lib/features/map/domain/enums/trip_status.dart. This prevents presentation/domain code from depending directly on Google API details.

External Data Integration

Concrete implementations call mapping APIs and map responses into feature models: lib/features/map/data/services/places_service_impl.dart, lib/features/map/data/services/directions_service_impl.dart, lib/features/map/data/models/place_prediction.dart, and lib/features/map/data/models/route_info.dart. Google Maps/Places are the material external services; Dio is the HTTP client. API credentials also cross native boundaries via android/app/src/main/AndroidManifest.xml and ios/Runner/AppDelegate.swift.

State and Control Flow

lib/features/map/presentation/bloc/map_bloc.dart owns the reactive flow: location/map initialization, destination-search results, route calculation, and transitions through TripStatus. Events originate from presentation pages, invoke injected domain services, then emit state consumed by map and ride UI. The Bloc is the primary orchestration boundary between asynchronous services and rendering.

User-Facing Flow

The home/map flow is assembled in lib/features/map/presentation/screens/home_screen.dart and rendered through lib/features/map/presentation/pages/map_page.dart. Destination selection is handled by lib/features/map/presentation/pages/search_destination_page.dart; route/trip controls are surfaced through lib/features/map/presentation/widgets/uber_bottom_sheet.dart. Google Maps Flutter provides the native map surface, while marker and geometry utilities support map rendering in lib/core/utils/map_custom_marker.dart and lib/core/utils/map_helpers.dart.

Runtime and Platform Infrastructure

The app targets Flutter/Dart 3.x with native Android Gradle and iOS Xcode runners. Native map SDK configuration and permissions belong to android/app/src/main/AndroidManifest.xml and ios/Runner/Info.plist. The architecture currently represents a client application: no backend, persistence store, authentication provider, or dispatch service is present in the repository structure.