How abhayjaiswar-gif/mq-parent-app works
This is a React Native fitness and sports app centered on a student-facing dashboard. The main workflow moves from welcome and account screens into the app’s tab navigation, where users can view fitness summaries, challenges, and a second-hand equipment bazaar; separate screens cover history, profile, scheduling, and video reels. Dashboard fitness visuals are implemented by reusable SVG diagrams. The excerpts show UI composition and local screen state, but no backend or persistent data layer. Some screen links are supported only by App.js’s indexed imports; ScheduleTab’s integration is not shown.
Main entry points: App.js App shell · DashboardTab.js Dashboard · LoginScreen.js Login · SignupScreen.js Signup
Components 15
App navigation
- App shell
App.js
Fitness insights
- Dashboard
components/DashboardTab.js - Analysis report
components/StatsTab.js - Activity history
components/HistoryTab.js - Fitness diagrams
components/diagrams - Schedule
components/ScheduleTab.js
Challenges and media
- Challenges
components/ChallengeTab.js - Reels
components/ReelsTab.js
Account screens
- Welcome
components/WelcomeScreen.js - Login
components/LoginScreen.js - Signup
components/SignupScreen.js - OTP verification
components/OtpVerifyScreen.js - Profile
components/ProfileTab.js
Marketplace
- Equipment bazaar
components/ShoppingTab.js
Other components
- Student
Connections 14
- Student → App shell: opens
- App shell → Welcome: renders
App.js - App shell → Login: routes to
App.js - App shell → Signup: routes to
App.js - App shell → OTP verification: routes to
App.js - App shell → Dashboard: renders
App.js - App shell → Challenges: renders
App.js - App shell → Equipment bazaar: renders
App.js - App shell → Analysis report: renders
App.js - App shell → Activity history: renders
App.js - App shell → Profile: renders
App.js - App shell → Reels: renders
App.js - Dashboard → Fitness diagrams: renders
components/DashboardTab.js - Login → Signup: offers link
components/LoginScreen.js