How sucodelarangela/tech-challenge-flutter works
Project type and purpose
• This is a cross-platform mobile (and web/desktop) financial management app built entirely in Flutter.
• It allows users to authenticate (via Firebase Auth), view/add/edit/delete financial transactions (stored in Firestore), and upload/download attachments (via Firebase Storage).
File structure
• Top-level “android/”, “ios/”, “macos/”, “linux/”, “windows/”, “web/” directories → native shells for Flutter.
• “lib/” → Dart application code, subdivided into:
• components/ (UI building blocks for filters)
• core/models/ (data schemas: AccountUser, Transaction, etc.)
• core/providers/ (state management: AuthProvider, TransactionProvider)
• core/services/ (Firebase integration: AuthService, TransactionService)
• screens/ (main pages: Splash, Login, Home, Transactions, Form)
• widgets/ (reusable UI widgets)
• utils/ (helper functions and routing)
• assets/ → fonts, images.
• pubspec.* → dependency configuration.
Key README insights
• Uses Provider for state management.
• Relies on Firebase (Auth, Firestore, Storage).
• Includes common UI libraries (flutter_slidable, loader_overlay), media plugins (image_picker, compress, gallery_saver), networking (dio), and utilities (intl, uuid).
Main components of the system
a. Client (Flutter engine) running on each platform
b. UI Layer: Screens → Widgets → Components
c. State Layer: AuthProvider, TransactionProvider
d. Service Layer: AuthService, TransactionService
e. Data Models: account_user, transaction, user_balance, etc.
f. External Systems: Firebase Auth, Firestore DB, Cloud Storage
g. Native Plugins: Image Picker, Permissions, Dio
Relationships and interactions
• User taps UI → UI widget calls Provider method → Provider calls Service → Service invokes Firebase SDK → Firestore/Storage responds → Service returns data → Provider updates state → UI rebuilds.
• Image attachment flow: Widget → ImagePicker plugin → local file → Service.uploadToStorage → Storage URL → Firestore transaction document.
Architectural patterns and design principles
• Layered Architecture (UI / State / Services / External API)
• Provider pattern for unidirectional data flow (MVVM-like)
• Single codebase targeting multiple platforms (CI/CD flows compile to native shells)
• Separation of concerns: Models ↔ Services ↔ Providers ↔ UI
Relevant technologies/frameworks
• Flutter & Dart
• Provider (state management)
• Firebase Core, Auth, Firestore, Storage
• flutter_slidable, loader_overlay (UI)
• image_picker, flutter_image_compress, image_gallery_saver_plus
• dio, permission_handler
• intl, uuid, path (utilities)
Be very detailed
• Path of a transaction CRUD operation end-to-end.
• Error flows (AuthException model) where relevant.
• How filtering uses utils/filter_utils.