How aarushk09/satez works
Project Type and Purpose
• SATez is a cross-platform SAT preparation platform (mobile & web) built with React Native (Expo) and TypeScript.
• It offers practice modules (vocab, reading, quizzes), AI-powered tutoring (GROQ API), progress tracking, and user management via Supabase (Auth, PostgreSQL, real-time).
File Structure
• app/: Expo Router pages & layouts, split into:
• (auth)/ → login & signup flows
• (tabs)/ → main tabbed interface (home, practice, quiz, tutor, resources, stats, profile, etc.)
• context/ → React Context providers (AuthContext, PracticeDataContext)
• components/ → app-specific screen components
• components/: reusable UI building blocks (Button, Card, ProgressBar, ChatMessage, SkeletonLoader, etc.)
• utils/: data-layer & integration
• supabase.ts → Supabase client setup
• groq.ts → AI tutoring integration
• storage.ts → AsyncStorage utilities
• database_setup.sql, setupSupabaseTables.js → DB schema & provisioning
• data/: static content (vocab.json, parsed SAT questions)
• assets/: fonts & images
• scripts/: project utilities (reset scripts)
• Config files: package.json, tsconfig.json, metro.config.js, eslint.config.js
README for Additional Insights
• Technology stack: Expo/React Native, TypeScript, Supabase, React Navigation, React Context, AsyncStorage
• Architectural pattern: client-centric, component-based, context/state management, service integration
• External services: Supabase Auth & DB, real-time subscriptions, GROQ AI API
Main Components & Their Relationships
a. Client (React Native + Expo Router)
• UI Layer: screens (app/(tabs), app/(auth)), layouts, shared components
• Navigation: Expo Router → handles auth flow and tabbed main flow
• State Management: React Context + custom hooks for auth state, practice data, theme, etc.
• Offline Layer: AsyncStorage for local persistence
• Data Layer: utils/supabase.ts and utils/groq.ts for remote calls
b. Backend (Supabase)
• Auth: email/password & OAuth → user_profiles table
• Database (PostgreSQL): practice results tables (vocab_practice_results, reading_practice_results, etc.)
• Real-time: subscriptions for live sync
c. AI Service (GROQ API)
• Chat-based tutor interface → ChatMessage component communicates with GROQ via utils/groq.ts
d. External Assets & Scripts
• Static data (assets/, data/)
• Provisioning: database_setup.sql, setupSupabaseTables.js
Architectural Patterns & Design Principles
• Layered architecture: Presentation → State (Context) → Data (utils) → External services
• Componentization: reusable components (components/ui, components/…)
• Separation of concerns:
• auth vs main flows (app/(auth) vs app/(tabs))
• data integration vs UI
• Offline-first design: AsyncStorage syncing with Supabase
Final Checklist
• [ ] Clear labels for each module, service, and data store
• [ ] Note key technologies next to components (e.g., “React Context”, “Expo Router”, “Supabase Auth”)