How arshnoor-singh-sohi/reddit works
Project Type and Purpose
• Full-stack, cross-platform social media app (Reddit clone)
• Flutter UI for Android, iOS, Web, Desktop
• Firebase backend: Auth, Firestore, Storage
• State management via Riverpod, routing via Routemaster
High-Level Architecture Layers
1. UI Layer (Flutter Screens & Widgets)
2. Business Layer (Controllers / StateNotifiers)
3. Data Layer (Repositories)
4. Firebase Layer (Auth, Firestore, Storage SDKs)
Main Components & Their Placement
• Platforms Boundary
– Android, iOS, Web, Linux, macOS, Windows host the Flutter engine
• UI Layer (inside Flutter engine)
– Feature Modules: Auth Screens, Community Screens, Feed Screen, Post Screens, User Profile Screens, Home Screens
– Core Widgets: PostCard, Loader, SignInButton, ErrorText
– Responsive & Theme utilities
– Router (Routemaster)
• Business Layer
– Controllers (AuthController, CommunityController, PostController, UserProfileController, ThemeNotifier)
– Expose StateNotifierProvider or StreamProvider via Riverpod
• Data Layer
– Repositories (AuthRepository, CommunityRepository, PostRepository, UserProfileRepository, StorageRepository)
– Abstract Firestore/Storage operations
• Firebase Layer
– FirebaseAuth, FirebaseFirestore, FirebaseStorage SDK instances
– Google Sign-In provider
– firebase_options.dart configuration
Relationships & Data Flows
• User ⟶ UI Screens: tap, input, navigation
• UI Screens ⟶ Controllers: call methods like signInWithGoogle(), createPost(), joinCommunity()
• Controllers ⟶ Repositories: invoke data methods (e.g., authRepository.signInWithGoogle())
• Repositories ⟶ Firebase SDKs: CRUD operations on Firestore collections (users, communities, posts, comments), file uploads to Storage, Auth calls
• Firebase SDKs ⟶ Firestore/Storage/Auth: persistent data stores and user management
• Firestore SDK ⟶ Controllers/UI via Streams: real-time updates (feeds, comments)
External Services & Hosting
• Google Sign-In (OAuth)
• Firebase Hosting or Vercel (for Web demo)
• Optional: Firebase Emulator suite for local testing
Architectural Patterns & Principles
• Layered architecture with strict separation of concerns
• Feature-first directory structure
• Reactive state management using Riverpod providers
• Single source of truth: Firestore as main data store
• Clean controllers that only handle UI logic, repositories abstract data sources