geezdock/voyaq

Purpose and runtime

VOYAQ is a Next.js 16/React 19 collaborative group-travel planner for Indian students. It supports squad creation and invitations, consensus planning, destination intelligence, trip status, and shared expense settlement. The App Router is the application entry surface: src/app/layout.tsx, src/app/page.tsx, and src/proxy.ts (authentication middleware).

Route domains and user entry points

Public flows include landing, authentication, squad creation/joining, tools, travel intel, and consent: src/app/auth/page.tsx, src/app/create/page.tsx, src/app/join/[code]/page.tsx. Authenticated/dashboard flows expose squads and profiles through src/app/(dashboard)/layout.tsx and src/app/(dashboard)/dashboard/page.tsx. Per-squad planning and finalized trip views are parameterized routes at src/app/workspace/[id]/page.tsx, src/app/trip/[id]/page.tsx, and src/app/trip/[id]/hub/page.tsx.

Identity, tenancy, and persistence boundary

Supabase supplies PostgreSQL, Auth, and Realtime; client and server access are separated in src/services/supabase/client.ts and src/services/supabase/server.ts. Shared authentication and selected-squad state are propagated through React providers: src/shared/providers/AuthContext.tsx and src/shared/providers/SquadContext.tsx. Database evolution and security policy are encoded in supabase/migrations/00001_initial_schema.sql, supabase/migrations/00002_rls_gaps.sql, and supabase/migrations/00006_fix_rls_recursion.sql; RLS is therefore a core tenant/access boundary. Development can bypass auth, and the app can run against mock/fallback data.

Squad planning workflow

Workspace UI implements the consensus pipeline: membership, destination proposal/voting, date voting, anonymous budget alignment, and custom polls. The orchestration surface is src/features/workspace/components/WorkspaceView.tsx; discrete stages live in src/features/workspace/components/steps/TabSquad.tsx, src/features/workspace/components/steps/TabDestinations.tsx, and src/features/workspace/components/steps/TabDates.tsx (with budget/polls sibling steps). Completion feeds the trip route, whose summary/status UI is src/features/trip/components/TripView.tsx.

Server actions and domain repositories

Mutation/read coordination is concentrated in server actions rather than exposed API-route files: src/actions/data.ts handles application data operations and src/actions/ai.ts handles AI-backed requests. Repository adapters isolate persistence concerns for squads and expenses: src/lib/repositories/squad.ts and src/lib/repositories/expense.ts. Types at src/types/squad.ts and src/types/expense.ts establish shared domain contracts across UI, actions, and storage.

Destination intelligence and AI

The destination hub is a tabbed aggregation boundary for weather, food, places, events, safety, transport, budget, itinerary, maps, and AI suggestions. Its shell is src/features/destination/components/DestinationHub.tsx, with representative panels src/features/destination/components/Weather/HubWeather.tsx and src/features/destination/components/AISuggestions/HubAISuggestions.tsx. Google Gemini is optional for itinerary, tips, and budgeting via src/actions/ai.ts; destination constants and typed data constrain this domain in src/constants/destinations.ts and src/types/destination.ts.

Expenses, tools, and client persistence

Expense tracking collects items, derives per-person balances, settlement matrices, and payment QR output through src/features/expense/components/ExpenseTracker.tsx, src/features/expense/components/SettlementMatrix.tsx, and src/features/expense/hooks/useExpenses.ts. Standalone planning tools are browser-oriented and include local-storage packing state and a currency service with offline fallback: src/features/toolkit/PackingList.tsx, src/features/toolkit/CurrencyConverter.tsx.

Cross-cutting operations

Caching uses Upstash Redis when configured, with in-memory fallback in src/lib/cache.ts. Sentry initializes across client, server, and edge runtimes via sentry.client.config.ts, sentry.server.config.ts, and sentry.edge.config.ts; PostHog is integrated through src/shared/providers/AnalyticsProvider.tsx. PWA behavior is delivered by public/sw.js, public/manifest.json, and the navigation fallback src/app/offline/page.tsx.