How wyze69-sys/fitsync works
FitSync is a fitness-tracking web app whose main user workflow runs from account access through workout logging and nutrition/weight tracking to progress and gamification feedback. React pages call a central API client; Express routes dispatch requests to domain logic backed by MySQL. The README also documents weekly AI insights and a broad admin portal. Some domain implementations were not sampled, so those branches are represented at subsystem level and only linked where the README or source index supports the relationship.
Main entry points: routes.js API route registry · workoutService.js Workout logging · services API services · db.js MySQL persistence
Components 19
React client
- App routing
client/src/App.jsx - Auth context
client/src/context/AuthContext.jsx - Fitness pages
client/src/pages - API services
client/src/services - API client
client/src/services/apiClient.js
API and access
- Express API
backend/app.js - API route registry
backend/src/routes/routes.js - Auth routes
backend/src/routes/authRoutes.js - Authentication
backend/src/services/authService.js - JWT access control
backend/src/middleware/authMiddleware.js
Fitness domains
- Workout logging
backend/src/services/workoutService.js - Nutrition planning
backend/src - Weight progress
backend/src
Progress and engagement
- Streaks and badges
backend/src/services/gamificationService.js - Weekly insights
backend/src/services/aiService.js
Platform operations
- Admin portal
backend/src/routes/adminRoutes.js - MySQL persistence
backend/src/config/db.js
Other components
- Member
- Google Gemini
Connections 22
- Member → App routing: uses
README.md - App routing → Fitness pages: routes to
client/src/App.jsx - Member → Auth context: signs in
README.md - Auth context → API services: requests auth
client/src/context/AuthContext.jsx - API services → API client: uses
client/src/services/authService.js - API client → Express API: sends API requests
client/src/services/apiClient.js - Express API → API route registry: mounts
backend/app.js - API route registry → Auth routes: dispatches auth
backend/src/routes/routes.js - Auth routes → Authentication: dispatches
backend/src/routes/authRoutes.js - Authentication → MySQL persistence: reads and writes users
- API route registry → Workout logging: routes workout requests
- API route registry → Nutrition planning: routes nutrition requests
backend/src/routes/routes.js - API route registry → Weight progress: routes weight requests
backend/src/routes/routes.js - API route registry → Streaks and badges: routes gamification requests
backend/src/routes/routes.js - API route registry → Weekly insights: routes AI requests
backend/src/routes/routes.js - API route registry → Admin portal: routes admin requests
backend/src/routes/routes.js - Admin portal → JWT access control: requires authentication
backend/src/routes/adminRoutes.js - JWT access control → MySQL persistence: checks user
backend/src/middleware/authMiddleware.js - Workout logging → MySQL persistence: persists workouts
backend/src/services/workoutService.js - Workout logging → Streaks and badges: updates rewards
backend/src/services/workoutService.js - Weekly insights → Google Gemini: generates insights
README.md - Fitness pages → API services: loads fitness data
README.md