How ureca-corp/si-dallant-wallet-app works
Project type and purpose
• This is a multi-platform (Android/iOS) mobile wallet application built with Flutter named “si_dallant_wallet_app.”
• It uses Firebase as its backend for authentication and data storage (see firebase.json, android/app/google-services.json, ios/Runner/GoogleService-Info.plist, and lib/firebase_options.dart).
• The app’s core features (per file names) include user authentication, balance display (“mydallant”), transaction results, charting, and token swap/exchange.
File structure
• Top-level Flutter modules:
• android/ – native Android project (Gradle build files, manifest, resources)
• ios/ – native iOS Xcode workspace (Info.plist, AppDelegate.swift, assets, pods)
• lib/ – Dart source code
• assets/ – fonts and video resources
• firebase.json, pubspec.yaml – configuration, dependencies
• Within lib/:
• main.dart – app entry point and routing
• firebase_options.dart – Firebase initialization
• controller/ – state-management classes (auth_controller.dart, result_dl.dart)
• command/ – data-access layer (dallant_insert.dart, read_firebase.dart)
• screens/ – UI pages (login, signup, mainpage, charts, alerts, wallet views)
• Notice the MVC-style separation: Screens (View) → Controllers (Controller) → Commands (Model/Service).
README for additional insights
• No deeper architectural hints beyond Flutter + Firebase.