How erickosanchezj/madness-schedule works
Project type and purpose
• This is a full-stack Progressive Web App (PWA) for fitness studios, with two web front-ends (member app and admin panel), a real-time backend built on Firebase (Firestore, Auth, Cloud Functions), and offline/caching support via a service worker.
File structure
• Top-level UI assets:
• index.html (member experience)
• admin.html (staff dashboard)
• service-worker.js, manifest.json, vendor/, images/
• Firebase hosting and config:
• firebase.json, .firebaserc, firebase-config.js, sw-firebase-config.js
• build-config.js
• Serverless backend (Cloud Functions) in /functions:
• src/… .js for class generation and notifications
• lib/ pruning scripts
• functions/package.json
• Security & rules:
• firestore.rules, firestore.indexes.json
• Supporting files:
• AGENTS.md, admin-manifest.json, CNAME for custom domain
README for additional insights
• Two distinct user roles (members vs staff)
• Real-time data sync, push notifications, offline support
• Automated jobs for generating classes & reminders