How angelpidza/alas_chiquitanas_donaciones works
Project type and purpose
• This is a full-stack Flutter client application (mobile: Android, iOS; desktop: Linux, Windows, macOS; web) for managing donations.
• Although there’s no backend code here, the app clearly uses HTTP (via Dio) to interact with remote donation-management APIs.
File structure
• Top-level “android/”, “ios/”, “linux/”, “macos/”, “windows/”, “web/” directories: platform embed targets.
• “lib/” contains Dart code with a clear layered/DDD organization:
• core/ – shared utilities (constants, error handling, network client, use-case base class)
• features/ – feature modules (app, auth, donor, volunteer, main) each subdivided into:
– data (models, data sources, repository implementations)
– domain (entities, repository interfaces, use cases)
– presentation (UI screens, state providers, widgets)
• “injection_container.dart”: service locator/DI setup.
• “pubspec.yaml”/“pubspec.lock”: external dependencies (Dio, Freezed, Riverpod/Provider, Flutter SDK, etc.).
README
• Minimal description: “A new Flutter project.”
a. Main components
• Client (Flutter UI on mobile/desktop/web)
• State-management layer (Riverpod/Provider + Freezed)
• Domain/use-case layer
• Data layer (Dio HTTP client → remote REST API)
• Core utilities (error handling, constants, dependency injector)
• External services (REST donation API, authentication API)
b. Relationships and interactions
1. UI widgets/screens dispatch events to state providers.
2. Providers invoke domain use-cases.
3. Use-cases call repository interfaces.
4. Repository implementations in Data layer use DioClient to make HTTP calls.
5. Responses flow back through models → domain entities → UI state → screens.
c. Architectural patterns/design principles
– Layered Clean Architecture (presentation → domain → data → core)
– Dependency inversion: domain depends on abstractions, data implements repos.
– Service locator/DI via injection_container.dart
– Code generation (Freezed for immutability, Riverpod/provider generation for state)
d. Key technologies/frameworks/libraries
– Flutter for UI (Dar t)
– Dio for HTTP client
– Freezed for immutable data classes + union types
– Riverpod or Provider for state management (inferred from .g.dart providers)
– Clean Architecture pattern
– Platform channels handled by Flutter embed (Android/iOS/desktop)