How diogocunhacardoso/coinllector works
Project Type and Purpose
• It is not a client–server web app, but a client-only app that packages multiple target platforms (Android/iOS/macOS/Windows/Linux/Web) and persists data locally (Sqflite) while optionally calling out to remote APIs (coin info, Stripe).
File Structure
• Top-level folders:
• android, ios, macos, linux, windows, web — platform boilerplate
• lib — main application code
• pubspec.yaml/lock — Flutter package config
• Under lib/ we see a Clean Architecture partition:
• config/router, config/themes
• data/datasources (local files, local database, remote HTTP, Stripe)
• data/mappers, data/models, data/repositories
• domain/entities, domain/interfaces, domain/usecases
• presentation (views, providers, models)
• shared (UI components, enums)
• utils (service locator, common helpers)
• The presence of GetIt (service_locator.dart) and Provider, plus GoRouter reveals DI and navigation layers.
README for Additional Insights
• Confirms Clean Architecture as guiding principle.
• Core tech: Flutter, Sqflite, GetIt, Provider, GoRouter.
• Features: local persistence, remote stripe service, image picking, filtering, sorting, advanced statistics.