How profitble/glow works
Project Type & Purpose
• This is a full-stack mobile application (“UMAX Clone”), built with Expo/React Native on the client side and Supabase + serverless functions on the backend.
• Purpose: a “for-women” wellness/self-care app with user profiles, AI-driven recommendations, real-time updates, and subscription monetization.
File Structure
• Top level:
• .gitignore, README.md
• assets/ (fonts, images)
• The lack of a “src/” folder in the tree is an artifact of the excerpt; most app source lives under the Expo project root.
• Key indicators: React Native app (Expo), static assets separated, no custom backend code here (it relies on Supabase and Vercel).
README for Additional Insights
• Tech stack: Expo/React Native, Supabase (Auth, Storage, Realtime, PostgreSQL), Vercel Edge Functions, OpenAI API, RevenueCat, TypeScript, Sentry, EAS.
Main Components & Their Roles
a. Frontend (Mobile Client)
• Expo/React Native app with routing (Expo Router), state (Zustand), offline persistence.
• Error boundaries, asset upload/download.
b. Backend as a Service (Supabase)
• GoTrue Auth + RLS policies (user management & security).
• PostgreSQL database (persistent storage).
• Storage bucket (user photos, other assets).
• Real-time subscriptions (live UI updates).
c. API Proxy Layer (Vercel Edge Functions)
• Secure “AI” and other third-party integrations.
• Origin validation, rate limiting, secret injection.
d. External Services
• OpenAI API (AI features)
• RevenueCat API (subscription state & monetization)
e. Monitoring & CI/CD
• Sentry for error monitoring.
• Expo Application Services (EAS) for builds, OTA updates, and CI/CD.
Relationships & Data Flows
• Mobile → Secure API calls → Supabase Auth & Database
• Mobile ↔ Realtime Subscriptions ↔ Supabase
• Mobile → Asset Operations → Supabase Storage
• Mobile → Edge Function → OpenAI → Edge Function → Mobile
• Mobile → RevenueCat → Mobile (entitlements)
Architectural Patterns & Principles
• BaaS (“Backend for Frontend”) with Supabase
• Serverless compute for custom logic (Edge Functions)
• RLS for zero-trust data access
• Real-time, event-driven updates
• Offline-first & graceful error handling on client
• Zero client-side API keys (all secrets held in server/proxy)
• Separation of concerns: UI vs. data vs. compute vs. external integrations
Technologies & Frameworks to Call Out
• Expo/React Native, TypeScript, Zustand, React Error Boundary
• Supabase (Auth, Storage, Realtime, PostgreSQL)
• Vercel Edge Functions, OpenAI API, RevenueCat SDK
• EAS (build/deploy), Sentry (monitoring)