How arthurlopesmagalhaes/cinemaapp works
Project type and purpose
• This is a cross-platform mobile full-stack application built in React Native with TypeScript.
• Purpose: allow end users to browse movies, select sessions and seats, purchase tickets via Stripe, and enable admin users to validate tickets at entry using a QR code scanner.
High-level components
a. Mobile Client (React Native)
• Presentation layer: screens (src/screens/… ) and reusable components (src/components/…).
• State management: Zustand/Redux-like stores (src/stores/…) and reducer (src/reducers/ticketReducer.ts).
• Navigation: React Navigation (src/routes/…).
• Business logic & utilities: utils (src/utils/…), form schemas (src/schemas/…).
b. API Layer
• Supabase client (src/services/supabase.ts) — authentication, real-time database CRUD, and edge functions (supabase/functions).
• Stripe client (src/services/stripeAPI.ts) — payment intent creation and confirmation.
c. Backend (Supabase)
• Database: movies, sessions, seats, users, tickets tables (seeded via supabase/seed.sql).
• Auth: user sign-up, login, roles (admin vs customer).
• Edge Functions: custom server-side logic (e.g., ticket generation, QR code validation).
d. External services
• Stripe API for secure payments.
• (Optionally) any third-party Lottie animations or font assets hosted locally.
Relationships and data flows
• UI → State stores: user interactions update in-memory store (e.g., cart, session).
• UI/Store → Supabase client: fetch movies/sessions, sign in/up, write ticket records.
• Store → Stripe client: initiate payment, wait for confirmation → on success invoke Supabase update.
• Admin scan flow: Mobile QR scanner reads ticket ID → call Supabase function → validate and mark as used.
Architectural patterns and principles
• Feature-based directory structure (screens, components, services, stores) enforces separation of concerns.
• Unidirectional data flow: UI dispatches actions → updates store → triggers API calls → updates state/UI.
• Thin client model: most business rules (ticket creation/validation) live in server-side Supabase functions.
• Reusable UI components and theming (src/global/theme.ts) for consistency.