← Back to FitQuest

FitQuest — App Info

Sitemap, wireframes, architecture overview, and tech stack for the gamified fitness PWA.

Sitemap Structure

API Endpoints Backend

Wireframes UI Layout

9:41●●●
Dashboard

Mobile — Dashboard (375px)

Desktop — Dashboard (≥768px)

Data Flow Architecture

How data moves through the system:

Manual entry

Browser (PWA)
Express /api/workouts
PostgreSQL workouts
Gamification service
XP / Level / Badges

Health Connect webhook

Android HC Webhook
POST /api/health-connect/webhook
health_daily_stats + workouts
Steps card + Workouts

Habits & streaks

Goals page load
GET /api/habits
Query workouts + health_daily_stats
Auto-progress bars + streak

Telemetry

navigator.sendBeacon
POST /api/analytics/track
analytics_events (no PII)
telemetry.html

Tech Stack Implementation

LayerTechnologyPurpose
FrontendVanilla JS (ES2022) + PWASPA with service worker, offline support, install prompt
FrontendMaterial Symbols RoundedIcon library (Google CDN, variable font)
FrontendWeb Audio APISynthesized UI sounds (no audio files)
BackendNode.js + Express 4REST API server
BackendPostgreSQL 16Primary database — users, workouts, diet, habits, analytics
BackendRedis 7Session storage, rate-limit counters, caching
Backendbcrypt + JWTPassword hashing + stateless auth tokens
InfraDocker ComposeLocal + production orchestration (app, postgres, redis)
InfraNginxReverse proxy, TLS termination, static caching
IntegrationsGoogle Health ConnectAndroid webhook for passive step/workout data
IntegrationsFitbit OAuth2Workout + sleep data import


View live telemetry →  |  About FitQuest →  |  Back to app →