How ritesh2351235/kidolearn works
Project type and purpose
• KidoLearn is a full-stack, cross-platform learning platform comprising:
• A Web Dashboard (Next.js, TypeScript, Tailwind, Radix UI) for parents
• A Mobile App (Expo + React Native, TypeScript) for children
• A unified Backend API (Next.js API Routes, Node.js)
• A PostgreSQL database (Prisma ORM)
• Integrations with external services (Clerk for auth, YouTube Data API, OpenAI GPT-4)
File structure
• Top-level “app/” folder houses web front-end pages (App Router) and app/api/ for backend routes
• “components/” holds shared React UI elements (dashboard-specific vs generic UI)
• “lib/” provides server-side helpers (DB client, YouTube client, utilities)
• “prisma/” contains database schema and migrations
• “kids-mobile/” is a self-contained Expo monorepo for the mobile app
• Configuration files at root and in kids-mobile coordinate builds, linting, TypeScript, environment variables
README for additional insights
• Tech stack, data flow, database models, and deployment targets are explicitly described
Detailed coverage
• API domain as sub-components of the gateway (e.g., /api/videos, /api/children, /api/recommendations)
• Offline/online synchronization for the mobile app
• CI/CD flow: GitHub Actions → Vercel / Expo
• Environment variables and secrets management as minor callouts