How drakejcz6/ocpi_citas_app works
OCPI Citas is a Flutter app for booking appointments at the Cuban Industrial Property Office. The user enters through the app shell, browses services and cached availability, then books or manages appointments online; appointment status is server-owned. Pull sync refreshes local service and appointment data on startup, reconnect, or explicit refresh—not periodically. The README documents local profile storage and local reminders as additional capabilities. The supplied source excerpts cover only platform scaffolding, so edges below rely on README statements; unsampled implementation details and wiring are not asserted.
Main entry points: screens Appointment screens · sync_engine.dart Pull sync engine · app.dart App shell and routing · local_database.dart Sembast local database
Components 15
App entry
- Flutter bootstrap
lib/main.dart - App shell and routing
lib/app.dart - Onboarding
lib/features/onboarding
Appointments
- Appointment screens
lib/features/appointments/presentation/screens - Services and availability
lib/features/appointments - Booking rules and slots
lib/features/appointments/domain - Appointment repositories
lib/features/appointments/data/repositories
Local data and sync
- Connectivity
lib/core/connectivity - Pull sync engine
lib/core/sync/sync_engine.dart - Sembast local database
lib/core/database/local_database.dart - HTTP client and identity
lib/core/network
User extras
- Client profile
lib/features/client_profile - Notifications and reminders
lib/features/notifications
Backend
- Django API
Other components
- App user
Connections 21
- App user → Flutter bootstrap: launches
README.md - Flutter bootstrap → App shell and routing: starts
README.md - App shell and routing → Onboarding: routes to
README.md - App shell and routing → Appointment screens: routes to
README.md - App user → Appointment screens: uses
README.md - Appointment screens → Services and availability: browses
README.md - Appointment screens → Booking rules and slots: validates booking
README.md - Appointment screens → Appointment repositories: manages appointments
README.md - Appointment repositories → Sembast local database: reads cache
README.md - Services and availability → Sembast local database: reads cache
README.md - Appointment screens → Client profile: uses profile
README.md - Appointment screens → Notifications and reminders: uses reminders
README.md - Connectivity → Pull sync engine: triggers on reconnect
README.md - App shell and routing → Pull sync engine: triggers on startup
README.md - App user → Pull sync engine: requests refresh
README.md - Pull sync engine → HTTP client and identity: pulls updates
README.md - Pull sync engine → Sembast local database: updates cache
README.md - HTTP client and identity → Django API: calls API
README.md - Appointment repositories → Django API: writes online
README.md - Services and availability → Django API: fetches availability
README.md - Client profile → Sembast local database: stores locally
README.md