How breehaqasim/glowsense-skincare-beauty-consultancy-platform works
Project Type and Purpose
• This is a full-stack platform designed to connect users with skincare and beauty experts. It supports functionalities like personalized skincare recommendations, virtual video consultations (likely using WebRTC), product listings for makeup, and management dashboards.
• The README clearly indicates user, expert, and admin features, along with APIs for authentication, consultation scheduling, and product listings. The project integrates multiple technologies across the frontend and backend.
File Structure
• Top-Level Directories:
• Documentations: Contains various documents, including API definitions, high fidelity prototypes, and the Software Architecture Document. Use these to confirm detailed design decisions.
• backend: Contains main Python files (app.py, models.py) suggesting the primary server-side logic.
• frontend: HTML, JavaScript, and CSS files that build the client-side interface. A further "src" folder there indicates an attempt to organize styling or auxiliary script files.
• public: Likely used for static assets (images, text files, etc.) which may include sealed prototypes or assets for the UI.
• This file structure indicates a separation between frontend and backend, consistent with a full-stack application deployed likely on a VPS.
System Components
a. Frontend:
• Components like the landing page, login/sign-up pages, and user interface modules (e.g., pages for skincare analysis, expert matching, video consultation UI).
• Mention that this layer is built using HTML, CSS/Bootstrap, and JavaScript with responsiveness ensured by media queries.
b. Backend:
• Core server-side application (app.py) that processes business logic, handles API requests, and orchestrates interactions.
• Additional python modules (models.py) for data modelling and RESTful endpoints.
• That the backend supports APIs for login, submitting skincare concerns, matching experts, scheduling consultations, and fetching trending makeup products.
c. Database & Infrastructure:
• Hosting environment (DigitalOcean VPS) and note the usage of session-based authentication.
d. External Services & Modules:
• Payment processing gateways (Google Pay, Apple Pay, Credit Cards), and mention the integration with WebRTC for secure video consultations.
• Performance-critical modules potentially written in C++ integrated with the backend.
Defining Relationships and Data Flows
• Detail interactions where the backend queries or updates the database.
• External interactions such as:
• Payment gateway integrations.
• Video consultation service (WebRTC) connections between clients and experts.
• If applicable, include interactions related to session management (e.g., authentication and authorization flows).
Architectural Patterns and Design Principles
• Separation of concerns between the frontend and backend.
• Point out the RESTful API layer that decouples client interfaces from business logic.
• If details in the documentation suggest, you may also highlight patterns such as MVC in the backend or modular microservices if the system scales to different services.
• Security measures (SSL encryption, session-based authentication) and integration points for unit and integration testing.