How jomeva12/timeline-flutter works
Project type and purpose
• This is a cross-platform Flutter application (“timeline”) targeting mobile (Android, iOS), desktop (Windows, macOS, Linux) and web, using Firebase for backend services.
• The app’s domain revolves around managing “empresas” (companies), security (“master_key”), and “vuelos” (flights), with screens for importing flights, displaying timelines, and CRUD operations.
File structure
• Top-level platform folders: android/, ios/, linux/, macos/, windows/, web/—each contains native host code and build scripts.
• lib/: the Dart source code, subdivided into:
• models/ (data classes: empresa, vuelo, master_key)
• providers/ (state-management and data-access services)
• screens/ (UI pages: empresa, importacion, timeline, home)
• widgets/ (reusable UI components, bottom sheets, dialogs)
• firebase_options.dart (Firebase configuration)
• Configuration files: pubspec.yaml, firebase.json, platform build files (Gradle, Xcode, CMake).
README
• Boilerplate Flutter README with no custom architecture notes, implying we infer architecture purely from structure and conventions.