How tituski/sewlesew-mobile-app works
Overall Project Structure
• At the highest level, show two major blocks: Client (Flutter UI) and the underlying Platform-Specific layers (Android, iOS, etc.) that Flutter compiles to.
Main Components within the Flutter Application
• Presentation Layer: Cover all the UI pages and widgets found under lib/features/*/presentation. Indicate that each feature (e.g., authentication, campaign, donations, explore, user_profile) has its own presentation logic (using BLoC, Cubit, etc.).
• Domain Layer: For each feature, highlight the domain entities, use cases, and repositories (interfaces) defined under lib/features/*/domain. This layer dictates the core business logic and validations.
• Data Layer: This includes models, mappers, repositories (implementations), and services (both remote and local) as seen under lib/features/*/data. It handles external API interactions, data persistence, and conversion.
• Core & Config Modules: Display a separate “Core/Config” section representing shared constants, utility functions, theming, and routes. This supports all the feature modules.
• Dependency Injection: Notice the presence of injection_container.dart. Represent the DI container that wires up the various components (services, use cases, blocs, etc.).
Cross-Cutting Concerns and Additional Modules
• State Management: Emphasize that BLoC/Cubit is used extensively for managing presentation state (found throughout the presentation/bloc directories).
• Routing & Theming: Under lib/config, showcase that routing configuration and theme settings help manage navigation and the appearance across the app.
• External Data Sources: Indicate connections from the data layer to any remote APIs or local storage systems (such as token storage in auth or campaigns/donations services).