How vokuorg/voku works
Project Type & Purpose
• Full-stack (front-end heavy) web application.
• Purpose: Enable users to create/join video-chat rooms (peer-to-peer via WebRTC), plus a “random call” mode.
• Tech highlights: React, Context API, Firebase (signaling), WebRTC, Tailwind CSS (via CRACO), static hosting (Netlify/Vercel).
File Structure
– Top-level:
• public/ → static HTML, manifest, redirects (Netlify)
• src/ → React code
– src/components → UI elements (chat, video layout, controls, modals)
– src/contexts → global state (AppContext for user/room data)
– src/firebase.js → Firebase app initialization
– src/pages → page views (Home, CallRoom)
– tailwind.config.js, craco.config.js → styling/build overrides
– No custom backend code — relies on Firebase and direct browser-to-browser connections.
Extract Key Architecture Insights from README
– Peer-to-peer video calling → WebRTC data & media channels
– “Random call” matchmaking → probably managed by Firebase functions or Realtime Database
– Esperanto support / X-System translation → may use an external translation API (if implemented).
Main Components & How They Interact
a. Frontend (React SPA)
• AppContext for user identity, current room, settings
• Pages: Home (landing + create/join), CallRoom (video + chat UI)
b. Signaling & Matchmaking (Firebase)
• Auth (anonymous or email?)
• Firestore/Realtime DB for exchanging SDP offers/answers & ICE candidates
• Optional Cloud Functions for random pairing
c. Peer-to-Peer WebRTC
• Browser A ↔ Browser B media streams (video/audio)
• STUN/TURN servers (public or custom) configured in code
d. External Services
• Translation API (for X-System auto-translation in chat)
• Hosting/CDN (Netlify/Vercel) serving static bundle
e. Asset Hosting
• Static assets (fonts, sounds, images) in public/ and src/assets
Architectural Patterns & Design Principles
– Component-based UI (atomic React components)
– Context API for global state (avoids prop drilling)
– Single Page Application (client-side routing with React Router)
– Event-driven signaling (Firebase triggers client WebRTC setup)
– Separation of concerns: UI vs. signaling vs. media plane
– Component labels (e.g., “CallRoom.jsx”) where helpful for clarity.
– Group related components inside boundaries (e.g., “src/components/*” cluster).