How soumiksen/trackreps works
Project type and purpose
• This is a full-stack (client-heavy) Expo mobile application built with React Native and TypeScript.
• Purpose: a fitness/workout tracking app with user authentication, routine and workout management, chat functionality (likely AI-powered via a “gemini” service), and history tracking.
File structure
• Top-level:
• app/ – file-based routing (Expo Router) for screens and navigation layouts
• components/ – reusable UI components (buttons, cards, progress bars, etc.)
• context/ – React Contexts for global state (AuthContext, WorkoutContext)
• services/ – data-access modules encapsulating calls to Firebase (firebaseconfig.ts), AI service (gemini.ts), and CRUD operations (users.ts, routines.ts, workouts.ts)
• data/ – static or mock workout data
• screens/ – container screens that assemble components per route
• assets/ – fonts and images
• firebaseconfig.ts – Firebase initialization
• Patterns:
• Presentation layer separated into components (dumb) and screens (smart).
• Business logic encapsulated in Contexts + service modules.
• File-based routing under app/ for navigation.
• External dependencies: Firebase (Auth + Firestore), AI “gemini” API.
Readme insights
• Standard Expo starter. Emphasizes development via expo start, file-based routing.
• No built-in backend code, so project relies on external Firebase + AI API.
Elements
• Clear labels for each component (e.g., “AuthContext”, “firestore/users collection”)
• UI → Context → Service → Firebase/AI
• Firebase Auth events → AuthContext
• Firestore updates → WorkoutContext → UI
• Blue rectangles for UI components/screens
• Green for Context providers (business logic)
• Orange for service modules (data access)
• Purple clouds for external services (Firebase, Gemini)