How kishore-klassy/beebagui works
Project type and purpose
• This is a cross-platform Flutter application (“beebag”) targeting Android, iOS, Linux, macOS, and Windows.
• Its core UI and business logic live in Dart under the lib/ folder. The platform folders (android/, ios/, linux/, macos/, windows/) host the native embedder code that boots the Flutter engine and connects it to each OS.
File structure
• Top-level directories:
• android/, ios/, linux/, macos/, windows/ → platform embedder, native build scripts, manifests, and plugin registrants.
• lib/ → the shared Dart code:
– lib/main.dart → application entry point
– lib/components/ → reusable widgets (bottom_nav.dart, voucher_card.dart, etc.)
– lib/pages/ → screen widgets (homepage.dart, signup_page.dart, edit_profile.dart, etc.)
• assets/ → images and other static assets
• test/ → automated widget/unit tests
• pubspec.yaml/.lock → Dart/Flutter dependency declarations
• Configuration files: build.gradle, CMakeLists.txt, Xcode project files, flutter tool configurations.
README for additional insights
• The README confirms this is a starter Flutter project. There is no pre-existing backend or external API layer documented. The focus is on the client app scaffolding.