How sanaya27/novella-app works
Project type and purpose
• This is a full-stack, real-time “dating/chat” web application with AI-powered suggestions (“Novella”).
• The root is a monorepo containing:
• novella-app (React SPA frontend)
• novella-backend (Node/Express API + WebSocket server)
• Supporting docs (API integration, troubleshooting, MD guides)
File structure
• Top-level “novella-app” folder: React code under src/pages, src/components, context, utils, public for static assets (3D butterflies).
• Top-level “novella-backend” folder:
• config (DB config)
• controllers (chatController.js, etc.)
• middleware (auth, socketAuth)
• models (Member, Match, Message, ChatMessage)
• routes (REST endpoints: auth, members, matches, messages, heartSync, butterflies)
• src/server.js (entry point)
• utils (helpers, seedDatabase)
• Root also contains legacy “Components”, “Entities”, “Pages” directories, various demos and MD guides.
README
• Minimal: merely project name/taglines.
• Other MD files (API_INTEGRATION_GUIDE.md, NOVELLA_CHAT_AI_INTEGRATION.md) document integration with external AI services.
• Frontend (React SPA)
• Backend API & WS Server (Express + Socket.IO)
• Database (MongoDB)
• External AI Service (e.g., OpenAI)
• Static Asset Store (butterfly FBX/textures served via public folder or CDN)
• Frontend → Backend (REST calls for auth, profiles, matches, heartSync, butterflies)
• Frontend ↔ Backend (WebSocket for real-time chat messages)
• Backend → Database (CRUD on Member, Match, Message, ChatMessage models)
• Backend → AI Service (HTTP API for chat suggestions)
• Frontend ← Static Assets (3D butterflies)
c. Architectural patterns/design principles:
• Monorepo with clear separation: “novella-app” vs “novella-backend”
• MVC style in backend: routes → controllers → models
• Context API in React for global state (UserContext)
• Real-time communication via WebSocket + auth middleware
• Extensible “Entities” schema as JSON (graph-QL style)
d. Key technologies/frameworks:
• Frontend: React, React Router, Context API, JSX components
• Backend: Node.js, Express, Socket.IO, Mongoose (MongoDB)
• External AI: HTTP-based AI prompt system
• Deployment/config: .env, Dockerish scripts (setup.sh/.bat), seedDatabase.js
Detailed breakdown of essential elements
• Frontend:
• Pages: Home, Chat, Chatbot, Garden, HeartSync, etc.
• Components: ButterflyAnimation, ChatInput, SmartSuggestions
• Context: UserContext
• Backend:
• Routes: /auth, /members, /matches, /messages, /heartSync, /butterflies
• Controllers & Middleware: chatController.js, auth.js, socketAuth.js
• Models: Mongoose schemas for Member, Match, Message, ChatMessage
• Data flow:
• User signs up/logs in → POST /auth → JWT
• SPA requests profile data → GET /members/:id
• Real-time chat → WebSocket connect → join room → emit/receive chat messages
• When sending a message → backend may call AI Service → AI suggestions → SPA displays SmartSuggestions
• HeartSync: periodic heartbeat data → POST /heartSync → models store and return aggregated heart rate
• Butterfly animations: triggered by backend events or SPA state