How lunatic2good/video-conferencing-app works
Project type and purpose
• This is a full-stack Next.js (v13+) web application built with the App Router.
• It provides user authentication (sign-in/sign-up), meeting scheduling (upcoming, previous, personal room), and real-time call/recording features via the Stream API.
File structure
• Top-level “app/” directory holds all route handlers and layouts (Auth, Home, Meeting).
• “components/” contains reusable UI elements (buttons, lists, modals, pages).
• “components/ui/” houses low-level primitives (button, input, dropdown, toast).
• “hooks/” encapsulates data fetching logic (useGetCalls, useGetCallById, useToast).
• “providers/StreamClientProvider.tsx” wraps the app with Stream’s SDK client context.
• “actions/stream.actions.ts” defines direct calls to Stream’s REST/JS SDK for room creation, joining, etc.
• “middleware.ts” enforces auth on server-rendered routes.
• CSS & config: Tailwind + PostCSS configs, global stylesheet, font loading, and Next config.
Extract README insights
• Bootstrapped with create-next-app, uses Next.js built-in font optimization and recommends Vercel for deployment.
• No custom architecture docs—everything is implicit in file structure.
Detail
• Flow of data from user interaction all the way through action calls to the external Stream service and back.
• Don’t omit the middleware/auth step or the static assets/CDN layer.