How khushi17380/fashnow works
Project Type and Purpose
• This is a full-stack mobile client: a Flutter-based e-commerce application (“fashnow_”) targeting Android and iOS.
• The repo contains:
• android/ & ios/ folders (platform wrappers, Gradle/Xcode projects, Firebase config)
• lib/ folder (Dart UI and feature modules)
• pubspec.yaml (Flutter dependencies)
File-Structure Analysis
• Top-level “android/” and “ios/” directories hold the native shell, build scripts, platform-specific config, and Firebase (google-services.json).
• “lib/” houses all Dart code, organized by feature:
• Address&Payments
• CART (cart & wishlist)
• PRODUCTS (grid & detail pages)
• categories (beauty, kids, men, women)
• Authentication (login_page.dart, sign_in.dart)
• Search, Orders, About & Terms, FirstScreen, main.dart
• There’s no on-repo backend; the app likely consumes REST/Firebase services.
Key Insights from README
• Described only as a Flutter e-commerce starter.
• Presence of Firebase config implies use of Firebase Auth/Firestore/Cloud Functions for backend services.
Main Components
a. Presentation Layer (Flutter UI Screens)
• Feature modules (ProductGrid, ProductPage, Cart, Wishlist, Address Management, Payment, Orders, Search, Categories, About & Terms)
• main.dart and routing
b. Business Logic / State Management
• Services or BLoCs/Providers (even if not yet implemented, a placeholder for where state lives)
c. Data Layer
• Repositories that wrap API calls or Firebase SDK
d. External Services
• Firebase Auth, Firestore / Realtime Database, Cloud Storage
• Third-party payment gateway (e.g., Stripe or in-app purchase)
• REST/WebSocket APIs (if any)
e. Platform Shell
• Android native wrapper (Gradle, AndroidManifest)
• iOS native wrapper (Xcode project, Info.plist, Swift bridging header)
Relationships and Data Flows
• UI → State Management → Repositories → External Services
• Repositories ↔ Firebase SDK or REST API
• UI ↔ Native Platform (push notifications, in-app purchases)
• Initialization path: main.dart bootstraps Flutter Engine, binds to native shell.
Architectural Patterns & Principles
• Layered Architecture (Presentation → Domain → Data)
• Feature-driven modularization (each folder in lib/ is a self-contained feature)
• Dependency inversion: UI depends on abstract services; implementations talk to Firebase or HTTP.