How codewithmurli/real-time-chat-app works
Project type and purpose
• This is a cross-platform real-time chat application built with Flutter.
• It targets mobile (Android, iOS), desktop (Windows, Mac, Linux), and web.
• It uses Firebase for authentication, real-time data (Cloud Firestore or RTDB), storage, and Cloud Functions for server-side logic (e.g., push notifications).
File structure
• Top-level “android”, “ios”, “web”, “linux”, “macos”, “windows”: native runners for each platform, auto-generated by Flutter.
• lib/main.dart: application entry point.
• lib/core: app-wide constants and reusable UI widgets.
• lib/models: data models for User, Chat, Message.
• lib/providers: state-management layer (AuthProvider, ChatProvider, ThemeProvider) using Provider.
• lib/services: wrappers around Firebase SDKs (auth_service, chat_service, storage_service, notification_service).
• functions/: Node.js Cloud Functions for server-side tasks (index.js), likely handling push notifications.
(empty) README for architectural hints
• Although empty here, we know from file names that the app uses Firebase services heavily and follows a Provider-based MVVM pattern.