How adityaghate66-sketch/crowdliftt works
1. Overall shape
- This repo is a static, browser-only frontend made of multiple HTML pages, each paired with its own CSS and JavaScript file.
- There is no custom backend in the repo; backend-like behavior is outsourced to Supabase for realtime data and Open-Meteo for weather.
2. Page-level architecture
- The app is split into distinct user journeys:
- index.html / index.js / index.css: landing page
- login.html / login.js / login.css: sign-in
- signup.html / signup.js / signup.css: onboarding and account creation
- home.html / home.js / home.css: main dashboard
- exLibrary.html / exLibrary.js / exLibrary.css: exercise library
- biteclub.html / biteclub.js / biteclub.css: diet and nutrition tools
- about.html: informational page
- This is a multi-page app, not a single bundled SPA.
3. Primary interaction boundary
- The core product boundary is the gym crowd dashboard on home.html.
- Users check in/out, pick a muscle group, and view live crowd state for that gym segment.
- The dashboard is the central place where realtime crowd data, predictions, attendance history, and weather-derived advice come together.
4. Realtime data layer
- Supabase is the main external state store and sync layer.
- Crowd updates are written to Supabase when users check in/out, then broadcast back to all clients via realtime subscriptions.
- This creates a shared live view across users without any repository-hosted server code.
5. Weather integration
- home.js also calls the Open-Meteo API for Bengaluru weather.
- Weather data is combined with gym crowd information to generate a practical “gym crowd tip” or contextual suggestion.
- This is a separate external dependency from the crowd data path, so the dashboard has two independent async sources.
6. Derived analytics on the client
- Several features appear to be computed in the browser from user activity and/or stored records:
- crowd predictor for day/time
- weekly heatmap
- workout calendar
- streak tracker
- personalized 7-day workout plan
- These are likely client-side derived views, not separate services.
7. Onboarding and identity flow
- login.html and signup.html handle user entry into the app.
- The README says signup includes 2-step onboarding collecting age, weight, height, goal, and activity level.
- Those profile inputs feed later personalization in the dashboard and diet tools, making onboarding a key data-collection boundary.
8. Exercise library subsystem
- exLibrary.* is a self-contained content and discovery area for workouts.
- It covers 30+ exercises across six muscle groups and supports search/filter behavior.
- The search box uses debouncing, so this page is optimized for client-side filtering rather than server queries.
9. Nutrition / BiteClub subsystem
- biteclub.* is a separate nutrition module branded as BiteClub.
- It provides BMI, BMR, and TDEE calculators plus meal-plan content.
- This feature set is independent from the crowd dashboard, but it likely uses the same onboarding profile inputs for personalization.
10. Navigation and shared presentation
- Each page has its own stylesheet, which suggests page-scoped styling rather than a shared component system.
- The architecture is intentionally simple: page-specific JS drives DOM behavior, page-specific CSS controls layout and theme, and HTML provides the entry point for each subsystem.
11. Runtime model
- The entire app runs in the browser using vanilla JavaScript, fetch, async/await, DOM events, and standard client-side state.
- There is no evidence of a framework, bundler, or compiled frontend layer.
- Deployment is via Netlify, which fits the static-site model.
12. Key data flows for an architecture diagram
- User → login/signup → profile/onboarding data
- User → home dashboard → Supabase write → realtime broadcast → other clients
- Home dashboard → Open-Meteo → weather/tip UI
- User activity/attendance → client-side derived analytics → calendar/streak/predictor
- User inputs → BiteClub calculators → nutrition outputs
- Search/filter input → exercise library → filtered exercise cards
13. Architectural takeaway
- CrowdLift is best understood as a static multi-page frontend with BaaS-backed realtime sync.
- Its main separation is by feature area: crowd tracking, exercise reference, nutrition tools, and onboarding/landing pages.
- The only external system-level dependencies are Supabase for shared state and Open-Meteo for weather enrichment.
Main entry points: home.html Dashboard · index.html Landing · home.js Check-in flow · login.html Login
Components 19
Entry & auth
Landing, sign-in, signup, and about pages
Crowd dashboard
Main gym crowd experience and live data flow
- Dashboard · Main crowd dashboard
home.html - Check-in flow · User check-in/out and muscle-group selection
home.js - Realtime sync · Supabase-backed live updates across clients
home.js - Weather fetch · Open-Meteo lookup for Bengaluru weather
home.js - Crowd tip · Weather-aware gym crowd suggestion
home.js - Derived views · Predictions, heatmap, calendar, streaks, and workout plan
home.js
Reference tools
Exercise library and nutrition utilities
- Exercise library · Workout reference and discovery page
exLibrary.html - Search filter · Debounced search and muscle-group filtering
exLibrary.js - Exercise catalog · 30+ exercises across six muscle groups
exLibrary.js - BiteClub · Nutrition and diet tools
biteclub.html - Calculators · BMI, BMR, and TDEE calculations
biteclub.js - Meal plans · Diet guidance and meal-plan outputs
biteclub.js
External services
BaaS and weather dependencies
- Supabase · Shared state store and realtime backend substitute
- Open-Meteo · External weather data provider
Connections 22
- Landing → Login: sign in · Landing page routes users into authentication
- Landing → Signup: join · Landing page routes users into account creation
- Landing → Dashboard: enter · Landing page can route to the main app
- Landing → About: about · Landing page routes to product information
- Login → Dashboard: authenticated · Successful login enters the dashboard
- Signup → Profile data: collects · Signup captures onboarding profile data
- Profile data → Dashboard: personalizes · Profile data influences dashboard guidance
- Profile data → BiteClub: personalizes · Profile data feeds nutrition tools
- Dashboard → Check-in flow: controls · Dashboard UI drives check-in and muscle-group selection
- Check-in flow → Supabase: write · Crowd changes are persisted externally
- Supabase → Realtime sync: broadcast · Realtime updates are delivered to connected clients
- Realtime sync → Dashboard: refreshes · Dashboard state updates from realtime events
- Dashboard → Weather fetch: requests · Dashboard fetches local weather
- Weather fetch → Open-Meteo: query · Weather data comes from Open-Meteo
- Weather fetch → Crowd tip: feeds · Weather data contributes to contextual advice
- Check-in flow → Derived views: inputs · Attendance and activity inform client-side analytics
- Derived views → Dashboard: renders · Predictions and history views are shown on the dashboard
- Dashboard → Crowd tip: shows · Dashboard presents the combined crowd tip
- Exercise library → Search filter: drives · Exercise library search and filters run in the browser
- Search filter → Exercise catalog: filters · Filtering narrows the exercise set
- BiteClub → Calculators: runs · Nutrition page performs body-metric calculations
- Calculators → Meal plans: produces · Calculator outputs inform meal-plan content