How genesis-ai-dev/langquest works
Project type and purpose
• LangQuest is a full-stack, offline-first mobile application (built with Expo/React Native) for collaborative language translation.
• The README describes local development with Docker + Supabase, use of PowerSync for offline sync, Drizzle for schema, and Expo Application Services (EAS) for CI/CD and builds.
File structure
• Top-level “app”, “components”, “views”, “navigators”, “contexts”, “hooks”, “providers” directories → client UI, navigation, and state layers.
• “database_services”, “db”, “drizzle”, “supabase” → data access layer, local schema definitions, migration scripts, Supabase backend (Postgres, Edge Functions, RLS).
• “supabase/functions” → Deno-based Edge Functions (clone-worker, send-email, sqltr).
• “.github/workflows”, “eas.json”, “tooling/github” → CI/CD pipelines (GitHub Actions, EAS preview/production deploy).
• “assets”, “supabase/assets” → static assets stored locally and in Supabase storage for audio/images.
• Config files (“app.config.ts”, “drizzle.config.ts”, “supabase/config.yml”) define runtime and sync settings.
README for additional insights
• Describes local dev environment orchestration (npm run env brings up Supabase/Postgres with Docker Compose).
• PowerSync replicates tables between remote and local DB.
• Supabase migrations and seeds under version control.
• Supabase Auth, Storage, Realtime, Edge Functions are core backend services.
• EAS build process for Android APKs and CI integration points.