How khaled280-313/cash_flow works
Project type and purpose
• This is a Flutter-based mobile application (“cash_flow”) targeting Android and iOS.
• It follows a feature-driven, clean-architecture style: each feature (auth, home, category, transactions, etc.) is split into presentation (Cubit/UI), domain (use cases, entities), and data (repositories, data sources).
• It includes a core layer for shared concerns (network connectivity, API client, cache helper, error handling, routing, theming, DI).
File structure
• Top-level “android” and “ios” folders contain native platform integration and build configurations.
• “lib” contains all Dart code:
• core/—shared services, network, caching, error definitions, utility widgets, service locator, routing, theming.
• features/—each feature sub-folder follows Data → Domain → Presentation folders.
– data/datasources: remote & local data source implementations
– data/model: DTOs
– data/repositories: repository implementations
– domain/entities & usecases: business rules
– presentation/cubit & pages/widgets: BLoC state managers and UI
• Third-party and generated code folders: dio_consumer, API interceptors, generated intl for localization.
• Configuration: pubspec.yaml, analysis_options, devtools_options, assets, fonts, images.