How amrsalahdev/fooddelivery works
Project type and purpose
• This is a cross-platform mobile/desktop Food Delivery application built entirely in Flutter (Android, iOS, web, Windows, macOS, Linux).
• It follows a feature-driven folder layout and implements a Clean-Architecture-inspired layering (presentation → domain → data) with Bloc/Cubit for state management, go_router for navigation, and a set of core services (authentication, location, toast).
High-level file structure analysis
• “lib/” holds all Dart source:
– “app/widgets” → shared UI controls
– “features/…” → each feature has sub-folders:
• “ui/screens” for Widgets and Bloc classes (presentation layer)
• “ui/cubit” (for login/register features) or none (stateless screens)
• “domain/usecases”, “domain/repo” → business logic interfaces
• “data/repo” → repository implementations
– “core/” → cross-cutting code:
• “services” (AuthService, LocationService, ToastService)
• “routes” (go_router config)
• “di” (dependency injection container)
• “main.dart” → app entry point, initializes DI, sets up Routing & Theme.
Key README insights
• Feature list: onboarding, login, register, home, cart management, checkout, order tracking.
• Packages: flutter_bloc, equatable, go_router, carousel_slider, toastification, etc.
• Design patterns: Bloc/Cubit, Clean Architecture.