How yasirabanuka/t-store--flutter-e-commerce-app works
Project type and purpose
• This is a Flutter‐based mobile e-commerce client (“t_store”) targeting Android and iOS.
• It provides user authentication, product browsing, cart & checkout flows, user personalization, and integrates with remote APIs (and Firebase services).
Main components
a. Mobile Shell & Flutter Engine
• Android (gradle, Manifest, Google services JSON)
• iOS (Xcode project, Podfile, GoogleService-Info.plist)
b. Presentation Layer
• Widgets & Screens under lib/features/ and lib/common/widgets/
• Navigation logic in lib/navigation_menu.dart
c. State Management & Business Logic
• GetX Bindings (lib/bindings/general_bindings.dart)
• Controllers in lib/features//controllers/
d. Data Layer
• Repositories under lib/data/repositories/** (authentication_repository, user_repository)
• Models under lib/features/personalization/models
e. Services & Utilities
• HTTP client (lib/utils/http/http_client.dart)
• Firebase setup (lib/firebase_options.dart, google-services.json, Podfile config)
• Cloud helper functions (lib/utils/helpers/cloud_helper_functions.dart)
• Local storage utility (lib/utils/local_storage/storage_utility.dart)
• Network management (lib/utils/helpers/network_manager.dart)
• Logging, formatting, exception handling, theming
f. External Services
• RESTful API endpoints (configured via lib/utils/constants/api_constants.dart)
• Firebase Auth / Firestore / Cloud Functions
Relationships & data flow
• UI Widgets ←→ Controllers (via GetX reactive bindings)
• Controllers → Repositories → Services → External APIs / Firebase
• Controllers ← Local storage for caching / persistence
• Services share utilities: network manager, HTTP client, exception transformers, logger
Architectural patterns & principles
• Feature‐based folder structure: each feature (authentication, shop, personalization) has its own screens/controllers.
• MVVM‐like layering:
– View = Flutter Widgets/Screens
– ViewModel/Controller = GetX Controllers
– Model = Data models & Repositories
• Dependency injection via GetX Bindings ensures components are instantiated and scoped per feature.
• Separation of concerns: UI, state management, data access, and external integration are decoupled.
• Theming & UI assets are centralized (lib/common/styles, lib/utils/theme, assets/...).
Technologies & frameworks
• Flutter (Dart)
• GetX (state management, routing, DI)
• HTTP (REST client)
• Firebase (Auth, Firestore, Cloud Functions)
• Platform SDKs (Android, iOS)