How brokoline/ocutuneapplication works
Project type and purpose
• This is a cross-platform Flutter application (“ocutune_light_logger”) for logging and analyzing users’ light exposure, managing patient/clinician messaging, and interacting with a BLE sensor. It bundles platform integrations for Android, iOS, Linux, macOS, Windows, and Web, uses a TensorFlow Lite model for light classification, and persists data locally with offline sync to a remote API.
File structure
• Top-level platform folders (android, ios, linux, macos, windows, web) contain native build and configuration.
• lib/ holds the Dart application:
• models/ – data representations
• controller/ – business-logic controllers managing state and coordinating services
• viewmodel/ – view models for MVVM binding (clinician, patient)
• services/ – abstractions over BLE, REST API, offline storage, classifier, error logging, sync scheduler
• screens/ & widgets/ – UI layer, organized by user role (customer, patient, clinician), registration flows, messaging, dashboards
• pubspec.yaml defines dependencies (flutter_tflite, HTTP, BLE libs, state-management if any)
README
• Confirms it’s a Flutter starter for a diploma project. No explicit architecture section—architecture is implied by the directory layout.
Key pointers
• Be exhaustive: include every major controller, service, and external dependency.
• Asynchronous flows: sensor polling, offline sync, message fetch.
• Assets (classifier model & matrices) feeding into LightClassifierService.
• With brief notes (e.g., “platform channel for BLE”, “periodic sync job”).