How hodayashirazie/collecta works
Collecta connects donors, drivers, and administrators through Flutter clients and Firebase-backed services. The principal flow is donor donation reporting: the client submits donation and pickup details, a Cloud Function records the donation and may assign it to a driver using activity-zone coverage; drivers then view routes and confirm pickups. Admin workflows cover donation and driver oversight, zone management, statistics, and driver impersonation. The Dart tree is documented in the README but absent from the supplied file tree, so client components use documented paths; backend links are limited to registrations and sampled calls.
Main entry points: admin_service.dart Admin service · index.js Function registry · reportDonation.js Report donation · daily_route_driver.dart Driver screens
Components 21
Flutter clients
- Donor screens
lib/ui/screens/report_donation.dart - Driver screens
lib/ui/screens/daily_route_driver.dart - Admin screens
lib/ui/screens/admin_homepage.dart - Donation service
lib/services/donation_service.dart - Route optimization
lib/services/route_optimization_service.dart - Admin service
lib/services/admin_service.dart
Donation operations
- Donation endpoints
functions/donations - Report donation
functions/donations/reportDonation.js - Activity zones
functions/activityZones - Driver profiles
functions/drivers - Route endpoints
functions/routes
Identity and profiles
- User roles
functions/users - Identity resolver
functions/utils/resolveUid.js - Function registry
functions/index.js
Firebase and integrations
- Cloud Firestore
- Firebase Auth
- Google Maps APIs
- Route optimizer
Other components
- Donor
- Driver
- Admin
Connections 27
- Donor → Donor screens: reports donations
- Donor screens → Donation service: submits details
- Donation service → Donation endpoints: calls endpoints
- Report donation → Cloud Firestore: writes donation
functions/donations/reportDonation.js - Report donation → Cloud Firestore: checks zone coverage
functions/donations/reportDonation.js - Report donation → Cloud Firestore: assigns driver stop
functions/donations/reportDonation.js - Driver → Driver screens: views route
- Driver screens → Route optimization: requests optimization
- Route optimization → Route endpoints: calls route function
- Route endpoints → Google Maps APIs: builds traffic matrix
functions/routes/computeRoutes.js - Route endpoints → Route optimizer: posts route inputs
functions/routes/computeRoutes.js - Driver → Driver screens: confirms pickups
- Driver screens → Donation service: submits pickup
- Admin → Admin screens: oversees operations
- Admin screens → Admin service: manages records
- Admin service → Donation endpoints: queries donations
- Admin service → Driver profiles: manages drivers
- Admin service → Activity zones: manages zones
- Admin service → User roles: verifies admin
- Function registry → Report donation: registers endpoint
functions/index.js - Function registry → Route endpoints: registers endpoints
functions/index.js - Function registry → Activity zones: registers endpoints
functions/index.js - Function registry → User roles: registers endpoints
functions/index.js - Driver profiles → Identity resolver: resolves identity
functions/drivers/updateDriverProfile.js - Identity resolver → Firebase Auth: verifies token
functions/utils/resolveUid.js - User roles → Cloud Firestore: stores role data
functions/users/syncUserWithRole.js - Activity zones → Cloud Firestore: reads zone data
functions/activityZones/getActivityZones.js