How astivens/temposagemovil works
Project type and purpose
• This is a cross-platform Flutter application (“temposage”) targeting mobile (Android, iOS), desktop (macOS, Windows, Linux) and web.
• Its focus is time-management and productivity: tracking activities, habits, tasks and time‐blocks, backed by local storage (Hive) and remote API calls, plus an on-device ML model for productivity prediction.
File structure
• Top-level platform folders (android, ios, linux, macos, windows, web): Flutter host configurations and platform-specific bootstrap code.
• lib/
└ core/: shared utilities—animations, constants, config, DI container, services (API, local storage, speech, notifications), Hive initialization, navigation.
└ features/: classic clean-architecture separation per domain (activities, auth, calendar, dashboard, habits, home, settings, tasks, timeblocks). Each feature splits into data (models, repositories, services), domain (entities, use-cases, services), and presentation (screens, widgets, controllers or cubits).
• assets/: fonts, images, and an on-device TFLite model with labels.
• Configuration files: pubspec.yaml, build.yaml, analysis_options.yaml, API_GUIDE.md, api_documentation.yaml.
README
• Minimal boilerplate Flutter README. No additional architecture notes, so infer architecture from directory conventions (Clean Architecture + Flutter best practices + hive for persistence + TFLite for inference).