How falconslayer51/whatsapp_ui works
Main Components
a. Client-Side (Mobile App):
• Present this as the top layer with separate modules for:
• Authentication Module
• Chat Module
• Status Module
• Calls Module
• Contact Selection Module
• Layout Management (Mobile/Web Responsive)
b. Backend Services:
• Firebase Services (evident from firebase_options.dart and google-services.json):
• Authentication Service
• Real-time Database/Firestore
• Firebase Storage
• Cloud Functions (if any)
c. External Services:
• Agora (for video/voice calls, indicated by agora_config.dart)
Architecture Patterns to Highlight
The project follows a clean architecture pattern with:
• Feature-based modular architecture
• MVC+Repository pattern within each feature
• Provider pattern for state management
┌─ UI Layer ─────────────────────────────────────┐
• Mobile Layout │ Web Layout │ Responsive Layout │
• Feature Modules ─────────────────────────────┐ │
• ┌─────────┐ ┌───────┐ ┌─────────┐ ┌────────┐ │ │
• Auth │ │ Chat │ │ Status │ │ Calls │ │ │
• ┘ └───────┘ └─────────┘ └────────┘ │ │
• Controllers/Providers ───────────────────────┐ │
• Repositories ─────────────────────────────────┤
• External Services ──────────────────────────────┤
• Firebase Services │ Agora Services │
• ┘
Important Details
a. For each feature module, show:
• Screens
• Controllers
• Repositories
• Models
• Widgets
b. Data flow indicators:
• User interaction flows
• API calls
• State management flow
• Storage operations
Specific Implementation Notes
Clear separation between:
• Authentication flow (login_screen → otp_screen → user_info_screen)
• Chat feature (mobile_chat_screen, chat_list, message handling)
• Status feature (status creation and viewing flow)
• Calls feature (voice and video call handling)
Cross-Cutting Concerns
Common components:
• Error handling
• Loading states
• File storage
• Shared widgets
• Utilities