How georgeyt9769/cardabase-app works
Project Type & Purpose
• Cardabase is a standalone, cross-platform mobile wallet app built with Flutter (Dart).
• It has no external backend—everything runs on the client, using encrypted local storage, camera/barcode plugins, and QR-based import/export.
High-Level Structure (from file tree & README)
• android/ → Native Android wrapper (Kotlin MainActivity, Gradle, platform integration, Fastlane)
• lib/ → Flutter code:
– data/ → Local DB schema & access (cardabase_db.dart)
– pages/ → UI screens (Home, Create/Edit Card, Barcode, Settings, etc.)
– theme/ → Theme definitions & providers (color_schemes, theme_provider)
– util/ → Business logic & services (camera, barcode read/write, import/export, vibration, UI tiles)
• fastlane/ → CI/CD scripts & metadata for Android releases
• submodules/flutter/ → Embedded Flutter engine
Key Architectural Patterns
• Layered architecture:
• Presentation Layer (lib/pages)
• State & Theme Management (Provider pattern in lib/theme & util/brightness_provider, theme_provider)
• Business Logic & Services (lib/util)
• Data Layer (lib/data with local SQLite/Drift, encrypted storage)
• Platform Integration (Flutter Engine ↔ Android via plugins)
• Flutter’s reactive UI + Provider for dependency injection and state propagation.
Main Components & Interactions
[UI Layer]
↕ uses
[State & Theme Providers]
↕ orchestrate
[Business Services (util)]
↔ call
[Platform Plugins] (camera, file I/O, barcode scanner)
↔ invoke
[Native Android APIs]
[Business Services]
↕ read/write
[Data Layer (cardabase_db.dart)]
↕ store/retrieve
[Encrypted Local SQLite DB]
[Build & Deploy]
Code → Flutter toolchain → Android Gradle → APK → Fastlane → Play Store (or F-Droid)
(GitHub Actions triggers android-release.yml)
• That the app is monolithic on the client, with no external web services.