How charls362/c-asistencias works
Project type and purpose
• This is a cross-platform Flutter application (“miapp”) targeting Android, iOS, Linux, macOS, Windows and Web.
File structure
• Top-level directories:
• android/, ios/, linux/, macos/, windows/, web/ → platform-specific embedding code and configurations.
• lib/ → shared Dart code: UI screens, routing, business logic, data access, PDF generation.
• test/ → widget tests.
• Core architecture folders under lib/:
• UI layer → *_screen.dart files (Widgets, navigation)
• Data layer → db_helper.dart, db_clase.dart (SQLite helper classes)
• Service layer → pdf_generator.dart (PDF creation)
• Entry point → main.dart (initialization, dependency injection, route setup)
• No explicit “backend” directory—this is a standalone client app using local storage.
README for additional insights
• It’s the auto-generated Flutter starter README. No custom architecture notes. We infer architecture purely from code and file layout.
Detail
• How main.dart bootstraps the app and wires up routes and services.
• Platform-specific plugin channels if any (e.g., sqflite native code in Android/iOS folders).