How intanaqilah-mf/kitatongtong works
Project type and purpose
• This is a cross-platform Flutter application (“projects”) targeting Android, iOS, Web, Linux, macOS, and Windows.
• It integrates with Firebase services (hosting, messaging, Cloud Functions) and also includes a standalone Node.js backend in lib/backend/server.js.
• The app provides user-facing pages (login, payments, package management, vouchers, staff management, etc.), and leverages Firebase Cloud Functions (in functions/) for server-side logic such as sending tax receipts.
File structure
• Top-level platform folders (android/, ios/, web/, linux/, macos/, windows/) contain the native shell for Flutter on each OS.
• lib/ holds the Dart code:
• lib/main.dart – Flutter entry point
• lib/firebase_options.dart – Firebase SDK configuration
• lib/pages/ – UI screens
• lib/widgets/ – reusable UI components
• lib/backend/ – custom Node.js server code
• functions/ contains Firebase Cloud Functions (JavaScript) for on-demand backend tasks.
• fix-firebase-urls/ is a utility script to patch hosting URLs.
• Configuration files: firebase.json, .firebaserc, pubspec.yaml, package.json.
README for additional insights
• Minimal README: boilerplate Flutter readme. No custom architecture docs.
a. Main components
• Flutter Client (multi-platform)
• Firebase Services
– Authentication
– Firestore / Realtime Database (if used)
– Cloud Messaging
– Hosting (serving the Web app)
– Cloud Functions (functions/)
• Custom Node.js Backend (lib/backend/server.js)
• Utility Scripts (fix-firebase-urls/)
• External Services (e-mail provider, payment gateways, etc.)
b. Relationships and interactions
– Flutter Client ↔ Firebase SDK (Auth, Database, Messaging) via REST/SDK calls
– Flutter Client → Cloud Functions (HTTP triggers) for tasks (sendTaxReceipt, fixPackageImages)
– Flutter Client ↔ Custom Node.js server for any non-Firebase APIs
– Cloud Functions ↔ Firebase database and external APIs (SMTP, payment processor)
– Utility scripts run during CI/deploy to update hosting URLs
c. Architectural patterns
– Frontend: MVVM or widget/page separation in Flutter
– Backend: micro-services split (Firebase Functions vs. standalone Node service)
– CI/CD: Firebase Hosting deploy for Web, native build pipelines for each platform
d. Technologies and frameworks
– Flutter/Dart for UI
– Firebase SDK (Auth, Firestore, Messaging)
– Firebase CLI & Hosting
– Firebase Cloud Functions (Node.js)
– Custom Node.js Express server in lib/backend
– build tools: Gradle, Xcode, CMake for desktops
Detail
• Every platform target under the Flutter block.
• Firebase service used.
• Where utility scripts fit into the deployment pipeline.
• Both serverless (Cloud Functions) and self-hosted (Node.js) backends.