How joshcarlouycaro/cudiamat works
This is a Flutter application whose documented description is only a project starter; the README does not specify its domain or user workflow. The tree indicates a dashboard, registration and summary screens, reusable dashboard/KPI/profile widgets, and an API service, but their runtime connections and behavior were not sampled. Native desktop runner relationships shown below are limited to references in the supplied source index and excerpts; no storage or external API behavior is inferred.
Main entry points: main.cpp Windows launcher · flutter_window.h Flutter window · main.cc Linux launcher · my_application.h Linux application
Components 14
Flutter app
- App entry
lib/main.dart - API service
lib/services/api_service.dart
User screens
- Registration
lib/screens/registration_screen.dart - Dashboard
lib/screens/dashboard_screen.dart - Summary
lib/screens/summary_screen.dart
UI components
- Dashboard tile
lib/widgets/dashboard_tile.dart - KPI card
lib/widgets/kpi_card.dart - Profile card
lib/widgets/profile_card.dart
Native runners
- Linux launcher
linux/runner/main.cc - Linux application
linux/runner/my_application.h - Windows launcher
windows/runner/main.cpp - Flutter window
windows/runner/flutter_window.h - Window host
windows/runner/win32_window.cpp
Other components
- User
Connections 4
- Linux launcher → Linux application: creates app
linux/runner/main.cc - Windows launcher → Flutter window: creates window
windows/runner/main.cpp - Windows launcher → Windows launcher: reads arguments
windows/runner/main.cpp - Flutter window → Window host: inherits window
windows/runner/flutter_window.h