aether-frame-creater/infinite-techfest-2026

Purpose and Current Scope

Infinite Techfest 2026 is an Expo/React Native symposium-management client for R.P. Sarathy Institute of Technology. The intended platform spans authentication, registrations, payments, QR attendance, certificates, dashboards, and administration, but the current implementation is centered on app shell, authentication, and a student home route. Planned backend data and most symposium workflows are not yet present.

Application Entry and Navigation

Expo Router provides file-based navigation. The root layout establishes application-wide routing and providers; app/index.tsx is the initial route. Route groups isolate unauthenticated and student experiences:

• app/_layout.tsx

• app/(authentication)/_layout.tsx

• app/(student)/_layout.tsx

Authentication routes cover onboarding, login, registration, email verification, and password recovery. The only domain-facing role route currently present is app/(student)/home.tsx.

Authentication Feature Vertical

Authentication is the most developed vertical slice. Route files delegate presentation to reusable auth screen components, while validation and remote operations are separated from UI:

• components/authentication/LoginScreen.tsx

• features/auth/schemas/loginSchema.ts

• services/authService.ts

The flow is email/password oriented: registration/login invoke the auth service, Supabase errors are translated for display, and recovery/reset/verification are modeled as distinct screens and Zod schemas. User data is normalized at the integration boundary in utils/mapSupabaseUser.ts.

State, Session, and Provider Boundary

App-wide concerns are intended to be composed through providers. AuthProvider owns session/auth-context lifecycle; the Zustand store supplies client-side auth state; QueryProvider establishes the server-state boundary for future data fetching:

• providers/AuthProvider.tsx

• store/authStore.ts

• providers/QueryProvider.tsx

Role-aware routing is implied by shared role definitions and separate route groups, but only student navigation exists today. Roles are represented centrally rather than embedded in screens: constants/roles.ts, types/role.ts.

Backend and External Integration

Supabase is the active external backend integration, expected to provide authentication and PostgreSQL-backed application data. Its client configuration and environment access are isolated from UI:

• lib/supabase.ts

• config/env.ts

• .env.example

The repository reserves database/ for future Drizzle schema, migrations, and seeds, but no database model files are currently present. Web cryptography compatibility is isolated in lib/webCryptoPolyfill.ts, an important runtime boundary for Supabase/auth behavior across Expo targets.

UI System and Cross-Platform Runtime

The client targets Android, iOS, and web through Expo. UI is intended to use NativeWind plus centralized theme tokens, with auth components constituting the current shared visual system:

• global.css

• theme/index.ts

• tailwind.config.js

Brand and authentication artwork are kept under assets/images/Branding and assets/images/Authentication. app.json is the Expo application/runtime configuration; metro.config.js and babel.config.js support bundling and transforms.

Intended Future Workflow Boundaries

The documented architecture separates lightweight route/UI layers from hooks/state, service-layer business operations, and integrations. Future event, payment, QR, notification, certificate, analytics, and admin capabilities should become feature-scoped modules and call services rather than access Supabase directly. Expected external capabilities include Expo Camera, Notifications, and pdf-lib, but these are roadmap dependencies rather than established repository components.